It is, but. You'll have to get used to running and searching via journalctl instead of processing the logs directly. Journal is not persistent across reboots by default, but you can reconfigure it to be. (just create /var/log/journal) Last I recall you won't get fine-grained per-daemon space controls on the logs, just a system-wide size and retention time for all journal entries.
Usually that's enough, but if all else fails you can fallback to another logger. On Thu, Sep 18, 2014 at 10:56 AM, walt <w41...@gmail.com> wrote: > I'm trying to track down a bad bug in dhcpcd-6.4.4, so (unlike most days > ;) I'm > paying close attention to the output of journalctl. > > The confusing part is that the output of journalctl is *very* different > depending > on whether dhcpcd starts correctly during boot. Or not. > > I think I may be shooting myself in the usual foot by continuing to use > sysklogd > along with systemd (using my own custom *.service script to start > sysklogd). > > If journald is really a complete syslog replacement then I'll dump my old > kludge > and be very happy to do it. > > Canek, maybe? Anyone? > > > > > -- This email is: [ ] actionable [ ] fyi [ ] social Response needed: [ ] yes [ ] up to you [ ] no Time-sensitive: [ ] immediate [ ] soon [ ] none
