>It's funny, for me it's the opposite - logging with systemd is sooo much better >than with Upstart. (IIRC, the logging of stderr of Upstart jobs was a >NixOS-specific hack, and other than that there was no logging support.)
Somehow, it work reliably… >However, there is a long-standing issue with stdout/stderr logging: if the >process dies before systemd has had a change to process its log message, then >systemd may not be able to figure out the unit corresponding to the message, so >it may be lost (or not attributed to the unit). See > > http://lists.freedesktop.org/archives/systemd-devel/2012-June/005590.html Apparently, the fix got merged? Why doesn't it work? Obviously, stderr of a failing service is the most interesting piece of logs on a personal notebook. >Also note that the journal has rate-limiting that may cause messages to be >dropped. I remember that story with flooding the kernel… _______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
