Comment 28 for bug 328881
Revision history for this message
| Clint Byrum (clint-fewbar) wrote Re: [Bug 328881] Re: init: support logging of job output | #28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
On Fri, 2011-03-11 at 07:12 +0000, Peter Funk wrote:
> This is a question from a third party software developer: I've to support a legacy application
> package which used to add an entry to /etc/inittab on traditional Unix/Linux systems to
> start (and respawn) a certain demon.
>
> When Ubuntu moved to upstart I added a /etc/event.d/-file template. Later I was forced to
> add an additional *.conf template for /etc/init directory. My question is: What do I have to put
> into these files to get the stderr output of this demon into the syslog on all versions of
> Ubuntu? (we have a lot of 8.04 LTS still in use in the field; moving slowly to 10.04 LTS)
> For me it is very difficult to figure this out. Thanks in advance.
> Is installing a backported upstart package a viable option? How much risk is that?
>
Peter, have you tried piping the output of the executed command to
logger?
As in
exec /usr/sbin/foobard | logger -t foobard
?