I'm trying to use Forever to keep my nodejs scripts up and running
As per Forever's homepage it says
[Long Running Process]
The forever process will continue to run outputting log messages to the console.
ex. forever -o out.log -e err.log my-script.js
[Daemon]
The forever process will run as a daemon which will make the target process start
in the background. This is extremely useful for remote starting simple node.js scripts
without using nohup. It is recommended to run start with -o -l, & -e.
ex. forever start -l forever.log -o out.log -e err.log my-daemon.js
forever stop my-daemon.js
However I fail to understand the difference between the two. Under what conditions should I use a long running process vs a daemon?
forever
will react to the console disapearing. If you want to use the 'Long Running Process' from an ssh session, your best bet is probably to run it in ascreen
or atmux
session – Frederik Deweerdt May 02 '13 at 04:40