| 1 |
It is, but. |
| 2 |
|
| 3 |
You'll have to get used to running and searching via journalctl instead of |
| 4 |
processing the logs directly. |
| 5 |
Journal is not persistent across reboots by default, but you can |
| 6 |
reconfigure it to be. (just create /var/log/journal) |
| 7 |
Last I recall you won't get fine-grained per-daemon space controls on the |
| 8 |
logs, just a system-wide size and retention time for all journal entries. |
| 9 |
|
| 10 |
Usually that's enough, but if all else fails you can fallback to another |
| 11 |
logger. |
| 12 |
|
| 13 |
On Thu, Sep 18, 2014 at 10:56 AM, walt <w41ter@×××××.com> wrote: |
| 14 |
|
| 15 |
> I'm trying to track down a bad bug in dhcpcd-6.4.4, so (unlike most days |
| 16 |
> ;) I'm |
| 17 |
> paying close attention to the output of journalctl. |
| 18 |
> |
| 19 |
> The confusing part is that the output of journalctl is *very* different |
| 20 |
> depending |
| 21 |
> on whether dhcpcd starts correctly during boot. Or not. |
| 22 |
> |
| 23 |
> I think I may be shooting myself in the usual foot by continuing to use |
| 24 |
> sysklogd |
| 25 |
> along with systemd (using my own custom *.service script to start |
| 26 |
> sysklogd). |
| 27 |
> |
| 28 |
> If journald is really a complete syslog replacement then I'll dump my old |
| 29 |
> kludge |
| 30 |
> and be very happy to do it. |
| 31 |
> |
| 32 |
> Canek, maybe? Anyone? |
| 33 |
> |
| 34 |
> |
| 35 |
> |
| 36 |
> |
| 37 |
> |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
This email is: [ ] actionable [ ] fyi [ ] social |
| 42 |
Response needed: [ ] yes [ ] up to you [ ] no |
| 43 |
Time-sensitive: [ ] immediate [ ] soon [ ] none |
Archives