On Wed, Nov 20, 2013 at 12:12 PM, Ralf Mardorf <[email protected]> wrote: > > Once you should use it again, please let me know how comfortable you're > with journalctl.
This is the second time in this thread that you criticize journald and I don't understand why. 1) If you're using systemd as pid 1, you can configure journald to forward all logs to rsyslog and not to store any logs in "/var/log/journal/". So you'll have all the usual logs in "/var/log/" (and only in "/var/log/") and you can read and process them as you've been doing for years. 2) journald nrgins with it a new tool, journalctl, to read logs. Using a new tool means that you have to learn some new skills and methods. If you want to isolate the logs of the last boot sequence, you can run "journalctl -b -1". If you want to check whether your your system shut down because it was overheating (as someone needed to on fedora-users recently), you can run "journalctl _KERNEL_SUBSYSTEM=thermal". Or you can run journalctl and grep your way to happiness. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAOdo=SyA_phMAQaK9F6prB=kua9fhx71i4nvyfbenrmirnc...@mail.gmail.com
