-
Notifications
You must be signed in to change notification settings - Fork 945
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
'forever list' don't list running scripts, --pidfile not effective #187
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've start with
forever start -p /usr/local/bin --pid /usr/local/bin/forever.pid -l /usr/local/bin/forever.log -o /home/node_app/alls.log -e /home/node_app/errors.log -a -d --sourceDir /home/node_app /home/node_app/app.js
but when list running scripts there's nothing
forever list
The "sys" module is now called "util". It should have a similar interface.
info: No forever processes running
Moreover, --pidfile is not effective, the pid file is still generated in user's home/.forever/pids. The example initd example is wrong with pidofproc is not a command.
I use latest forever installed with npm, node v0.6.4 on Red Hat Enterprise Linux Server release 5.2 (Tikanga).
The text was updated successfully, but these errors were encountered: