MartinWalter
unread,Jul 5, 2011, 11:49:26 AM7/5/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bluep...@googlegroups.com
Hi,
is it possible to let stdout/stderr of watched processes be logged to syslog in a reliable manner? Currently I see these possibilities which all have their drawbacks:
1) process.start_command = "/usr/bin/myapp 2>&1 | logger"
This would instruct bluepill to watch the shell which starts /usr/bin/myapp and logger as its children. When either of them is killed, bluepill wouldn't notice.
2) use process.stdout and process.stderr directives
Currently, stdout and stderr require a filename as an argument. Using syslog-ng, this file could then be read into syslog. This solution induces an undesired coupling between syslog-ng configuration and bluepill.
I'd love to see bluepill to be extended with the capabilities of the logger.rb component that's bundled with bluepill. However, my knowledge of ruby is very limited.
Thanks for your help,
Martin