FCGI scripts will not always restart when they are updated #58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- exit(0) was caused only when script file is updated: On binary distributions this assumption is not true. If would be caused anytime when timestamp is simply changed. - The time of startup was used for origin of change. Timestamp of script would be used instead. - Non-standard `SCRIPT_FILENAME` environment variable was referred. Instead use `$PROGRAM_NAMe` (`$0`).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
FCGI scripts (wwsympa.fcgi and sympa_soap_server.fcgi) will not always restart when they are updated.
SCRIPT_FILENAMECGI environment variable was referred. Instead use$PROGRAM_NAME($0).Note:
Restartdirective may be useful. With traditional sysVinit script, manual restart may be required.