IMO we should stop discussing systemd ;). JFTR
On Wed, 2013-11-20 at 13:11 +0000, Tom H wrote: > On Wed, Nov 20, 2013 at 12:12 PM, Ralf Mardorf > <ralf.mard...@alice-dsl.net> 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. Take a look at https://mailman.archlinux.org/pipermail/arch-general/2013-October/034284.html and follow ups. You're allowed to laugh at me, but there's another thread and this one isn't that funny. "Notice though that syslog-ng under systemd may have an incomplete log." https://mailman.archlinux.org/pipermail/arch-general/2013-October/034345.html and follow ups. Debian does use initscripts different, than Arch Linux did, but this was easy to understand and to handle. Systemd is hard to understand and if it should behave different for different installs, where are the scripts that I can read to understand what different distros do in a different way? Correct, there are no scripts anymore, everything is hidden, we need to be able to understand much more, to get skills just to handle systemd, even if we don't need'em for anything else. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1384954996.11280.19.camel@archlinux
