-
Notifications
You must be signed in to change notification settings - Fork 21
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
Make it easier to capture stderr #2
Comments
Not bad :) I guess its a matter of aesthetics. And also, since anyway its collating both However, I have a feeling there might be requests to capture |
I don't think this is the right move. The SOP in System V and upstart scripts is to start the service with output redirection. It keeps the process tree clean and makes using flags and piping cleaner and easier to read. |
Right, I am a fan of piping too. It feels like the natural unix approach. Its just that a few people have raised the concern that it should capture from |
From the README, to capture stderr, you need to do:
What if instead you could do:
funnel -cmd '/etc/myapp/bin'
? Then it could capture all stdout and stderr on its own.The text was updated successfully, but these errors were encountered: