On Sun, 06 Jul 2014 18:18:46 +0200 lee <l...@yun.yagibdah.de> wrote: > Kevin Fenzi <ke...@scrye.com> writes: > > > On Sun, 06 Jul 2014 09:52:24 +0200 > > lee <l...@yun.yagibdah.de> wrote: > > > >> Kevin Fenzi <ke...@scrye.com> writes: > >> > >> > output. With systemd/journald, ALL output is saved and easy to > >> > query. > >> > >> How do you query this output? I just look at the logfile, and when > >> it's not there, I never see it. What's the advantage of hiding > >> output like that? > > > > journalctl -u servicename > > > > (I usually add -b which gives you messages only since last boot). > > That doesn't make sense. What if you're trying to solve a problem, > suspecting a particular service, and the problem is somewhere else? > You'd never see the relevant messages because they remain hidden.
journalctl | grep whatever or journalctl | less and page though things? > You'd have to browse all messages, and an ordinary logfile is > perfectly suited for that. What's the advantage of using an > unreadable format and added complexity supposed to be? It lets you do things like easily grep the messages from just the last boot, or isolate things from particular services, export it in other formats, lets you easily log from containers or user space items. Anyhow, it sounds like you are pretty firmly set in your dislike for systemd/journald. Not sure continued discussion will change your mind any... kevin
signature.asc
Description: PGP signature
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
