Upgrade to daemonize 0.5.0 to get rid of boxfnonce #403
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
boxfnonce crate is obsolete since Rust 1.35 and cargo audit complains about it. daemonize 0.5.0 doesn't use it any longer but is incompatible with earlier version in that the exit_action() modifier is no longer supported. Despite the lack of any hint as to how to achieve the same thing with the newer version, it seems it can be done using daemonize.execute() instead of damonize.start(), since it will allow the parent to continue execution past the fork point. Signed-off-by: David Verbeiren <[email protected]>
|
this is a duplicate of #361. |
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.
boxfnonce crate is obsolete since Rust 1.35 and cargo audit complains about it. daemonize 0.5.0 doesn't use it any longer but is incompatible with earlier version in that the exit_action() modifier is no longer supported.
Despite the lack of any hint as to how to achieve the same thing with the newer version, it seems it can be done using daemonize.execute() instead of damonize.start(), since it will allow the parent to continue execution past the fork point.