Skip to content
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

always use full paths when starting scripts #367

Closed
wants to merge 1 commit into from
Closed

always use full paths when starting scripts #367

wants to merge 1 commit into from

Conversation

aMoniker
Copy link

In response to this issue.

There are two downsides I can see to this.

One is that the command-line output of forever list will now be a little bulkier.

The other is that some people might currently rely on the ability to stop identically-named scripts with a single command. However, that would mean they're relying on undocumented functionality that could be classified as a bug anyway.

@indexzero indexzero closed this in 6047462 Apr 21, 2013
@indexzero
Copy link
Member

So not taking this, because as you said its overly verbose in the simple case. But fret not! If you really care about this you can now do:

$ forever columns add dir
$ forever list
info:    Forever processes running
data:        uid  command             script                     forever pid   logfile                          uptime       dir                                          
data:    [0] b7z5 /usr/local/bin/node examples/server.js -p 8080 13998   13999 /Users/charlie/.forever/b7z5.log 0:0:3:26.508 /Users/charlie/Git/nodejitsu/forever-monitor

@aMoniker
Copy link
Author

Excellent, thank you. Until now I've relied on differentiating processes by the names of logfiles :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants