Kevin Fenzi kevin@scrye.com writes:
On Sun, 06 Jul 2014 09:52:24 +0200 lee lee@yun.yagibdah.de wrote:
Kevin Fenzi kevin@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.
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?