| Commit message (Collapse) | Author | Age |
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
This brings these functions closer to MAPC.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
Before this change, the variables would be unbound in IMAGE-DUMPED images.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
The name will show up in, e.g., top(1) inside containers.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Update stored checksums when reinvoking, else the SBCL-specific checks in
%DUMP-CONSFIGURATOR-IN-GRANDCHILD will always fail in reinvoked images.
- Also update *US* when reinvoking; previously, the code in IMAGE-DUMPED to
skip the dump when the target filename is the executable we're running from
was using the old value of *US* and thus would probably never skip the dump.
- Don't abort the dump just because the target filename is the executable
we're running from (I believe the restriction was accidentally included when
refactoring a previous work-in-progress version of fbe55a361f).
- %DUMP-CONSFIGURATOR-IN-GRANDCHILD: ensure we remove the hook which evaluates
the parent process's request so it doesn't get run again.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
SB-EXT:*RUNTIME-PATHNAME* is the path to the executable.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
|
| |
When SBCL fails to start up, such as when previously-loaded shared libraries
cannot be found while trying to reinvoke a dumped image, it exits 1. We must
avoid erroneously interpreting this as a successful attempt to make changes.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
| |
Previously we waited for waitpid(2) to return before reading from the pipes.
If either pipe filled up before the child process exited, we would deadlock.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
| |
In particular, reloads initiated by the call to ASDF:LOAD-SYSTEM in
CONSFIGURATOR.DATA.ASDF::SYSTEM-VERSION-FILES.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
CFFI outputs C toolchain commands it runs to *DEBUG-IO*.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
|
|
|
| |
Also replace some calls to chmod(1) with calls to chmod(2).
Using CFFI rather than implementation-specific wrappers should be better for
portability. Also with this commit we stop hard coding types like uid_t as
:UNSIGNED-INT, which was less portable.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
This should provide a performance improvement.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
This should enable depending on Lisp systems which use the CFFI Groveller.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
| |
See the RETURN-EXIT and WITH-BACKTRACE-AND-EXIT-CODE macros.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
| |
It's possible that the home directory or username have been changed since the
fork control child was created, perhaps by INSTALLER:CLEANLY-INSTALLED-ONCE.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
| |
This ensures that the fork control child is in the same context as its parent
-- for example, that they're both chrooted.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
| |
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
|
|
|
|
|
|
|
|
|
| |
Drop CAN-PROBABLY-FORK because we now only try to fork(2) in contexts in which
there shouldn't ever be any other threads running, apart from Lisp
implementation finaliser threads and the like.
We no longer need to RESET-DATA-SOURCES before CONTINUE-DEPLOY* because we now
only fork(2) in contexts in which *NO-DATA-SOURCES* is t.
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|
|
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
|