Typo fix for reexec related environ variables #2559
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Commit 1 is a refactor. The others are reexec environ related.### Commit 1MovedArbiter.log.close_on_exec()
fromArbiter.init_signals()
toArbiter.setup()
. Seem more appropriate.### Commit 2InArbiter.maybe_promote_master()
, cleanup more env variables passed fromArbiter.reexec()
called in parent.Considering whether to unsetLISTEN_PID
,LISTEN_FDS
is handled bysystemd.listen_fds(unset_environment=True)
underArbiter.start()
. I leave these two env vars alone.Commit 3
In
Arbiter.reexec()
,GUNICORN_FD
may not be passed to the new master process,Replace
GUNICORN_FD
withGUNICORN_PID
instead to detect whether a process is areexec
ed process.