Logging in future upstart
Casey Dahlin
cdahlin at redhat.com
Sun Mar 22 18:53:32 GMT 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Scott James Remnant wrote:
> On Sun, 2009-03-22 at 19:37 +0100, Matthias Urlichs wrote:
>
>> In fact, I just had an better idea: don't use a named pipe. upstart
>> could simply read the stderr of all processes it starts, store that in a
>> ring buffer, and feed a logger process from that (via stdin).
>>
>> Replace any lines which the logger doesn't read fast enough (i.e. the
>> ring buffer overflows) with a "<skipped>" marker. Auto-kill+restart the
>> logger if it doesn't want to read its standard input for too long.
>>
> This is pretty much what I'm thinking of doing - with the added bonus
> that we can keep hold of this buffer and send it elsewhere on failure
> like cron does.
>
> (email output to root when apached dies anyone?)
>
> Scott
>
Last time we talked about having Upstart itself do the reading you were
against it. Has this changed then?
- --CJD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAknGiSwACgkQIHOkVH4pLz5M5gCfWQQpRBbjn9bnKQeGWqMekeTc
6LAAoJOSFQ8xvw1r6WDe3EicSEwVBk1v
=5/pK
-----END PGP SIGNATURE-----
More information about the upstart-devel
mailing list