forked from Slashed/daemon.node
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarification on daemon management once daemon running? #39
Comments
I guess something like this (or a link to it) would have been nice: https://www.digitalocean.com/community/tutorials/how-to-write-a-linux-daemon-with-node-js-on-a-vps as the example here so far is rather incomplete in terms of overall daemon management. |
I don't actively maintain this module right now but would welcome a PR or some wiki pages to help guide new users. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm a new to *nix daemons and node.js. From the readme examples, it's not clear how the daemon management occurs once the daemon is started (running script forked and parent process exited). For example:
Best practices for the above questions for use of this daemon node module.
The text was updated successfully, but these errors were encountered: