On Tue, Sep 2, 2014 at 12:26 AM, Michael Raskin <[email protected]> wrote: >>As a sysadmin, I love systemd and journald. If you want to maintain lots of >>disparate things and look all over the OS while troubleshooting, good for >>you, but systemctl and journalctl make life so much easier. Upstart is a >>very poor substitute. > > What are the keys for journalctl to make it work? Because it wants to > read hundreds of megabytes of data just for showing me last 20 lines of > some log — way worse than tail. > > Also, could you submit a patch that makes systemd log stderr of services > reliably (stdout too)? We had it with Upstart, but with Systemd it got > lost and I am not sure how to make it automatic for all services. >
Well, what's make it unreliable? I think systemd always logs stdout/stderr. And it's seen with "journalctl -u NAME" and "systemctl status NAME". May be I've not logged hundreds of megabytes to systemd yet. Does't break when traffic is too high? -- Paul _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
