|author||Mark Hatle <firstname.lastname@example.org>||2011-10-26 16:51:34 -0500|
|committer||Peter Seebach <email@example.com>||2011-11-02 13:31:41 -0500|
Implement PSEUDO_UNLOAD, replacing existing PSEUDO_RELOADED semantics.
Change from internal PSEUDO_RELOADED to external PSEUDO_UNLOAD environment variable. Enable external programs to have a safe and reliable way to unload pseudo on the next exec*. PSEUDO_UNLOAD also will disable pseudo if we're in a fork/clone situation in the same way PSEUDO_DISABLED=1 would. Rename the PSEUDO_DISABLED tests, and create a similar set for the new PSEUDO_UNLOAD. Signed-off-by: Mark Hatle <firstname.lastname@example.org>
Diffstat (limited to 'pseudo.1')
1 files changed, 28 insertions, 11 deletions
@@ -408,8 +408,9 @@ client library does not modify the behavior of called functions, though it
continues to intercept them and block signals while processing them. This
variable is reevaluated on every call to
.IR fork(2) ,\ clone(2)
-or related functions. If the value starts with a lowercase or uppercase s,
-the pseudo client disables all server spawning and communications, but still
+or related functions. If the value starts with a lowercase or uppercase
+, the pseudo client disables all server spawning and communications, but still
operates locally. This means that no filesystem mode or permissions changes
are actually recorded or reported, but functions like
@@ -506,15 +507,6 @@ This variable is automatically set by the
program when it is used as a launcher.
-This purely internal variable is used to track state while trying
-to re-execute to get rid of the
-value when spawning a server. (The
-server itself cannot function running in the
-.I pseudo environment.)
If this variable is set in a client's environment, its value is
communicated to the server at the beginning of each client session,
@@ -526,6 +518,24 @@ associated with them; the tag value is per-client, not per-server.
These variables are used internally to pass information about the current
emulated user and group identity from one process to another.
+This variable is reevaluated on every call to
+.IR fork(2) ,\ exec(3)
+or related functions. If the variable exists
+will be removed from
+behavior will also be triggered. For processes
+the behavior will be the same as if
+was set. For new processes, after a call to
+.IR exec(3)\ or\ system(3)
+pseudo will not be loaded in the new process.
If set, this will be used when
@@ -566,6 +576,13 @@ than it is otherwise. This is probably because nearly every operation
communication with the server, and probably some kind of database
+wrapper unconditionallity restores the system environment. It also invokes
+the checks to see if the user has requested pseudo to be disabled or unloaded.
+Due to the semantics of clone, this causes both the parent and child processes
+to be disabled or unloaded.
.SH SEE ALSO
fakeroot(1), ld.so(8), pseudolog(1), sqlite3(1)
.SH FURTHER READING