1 |
Rich Freeman posted on Wed, 25 Feb 2015 07:13:03 -0500 as excerpted: |
2 |
|
3 |
> On Wed, Feb 25, 2015 at 5:13 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
4 |
>> |
5 |
>> a) If the system crashes, partially corrupted in-the-crash text logs |
6 |
>> can be of at least some use after a reboot. Binary journals, not so |
7 |
>> much. |
8 |
> |
9 |
> Have you tested this, or found some other data to support this? I think |
10 |
> that journalctl does parse truncated files. |
11 |
|
12 |
I believe I've seen posts to that effect on the btrfs list (my biggest |
13 |
non-gentoo participation). Note that journald does rotation of I believe |
14 |
8 journal files by default, and ideally, it'd only be the last one chewed |
15 |
up. Also, cleanly truncated is one thing; file-system-corrupted so it |
16 |
ends up with a piece of some other totally different file in it (as most |
17 |
more modern filesystems take pains to prevent, at least on Linux, as the |
18 |
other file might be from another user and that ends up being a security |
19 |
risk, so modern filesystems generally zero-truncate it if they think it |
20 |
might be corrupted in that manner) is something entirely different. |
21 |
|
22 |
However, fair point. My support on this bit /is/ a bit fuzzier than I'd |
23 |
like. Thanks for pointing that out, to me as well. =:^) |
24 |
|
25 |
>> But syslog-ng lets me dump them without ever actually logging them, or |
26 |
>> route them to a different log file if I prefer, keeping my primary logs |
27 |
>> clean. =:^) |
28 |
> |
29 |
> I was thinking about this and another advantage of split log files is |
30 |
> that you could have different rotation/retention policies for each. I |
31 |
> believe journald's log rotation is one-size-fits-all. |
32 |
|
33 |
I believe so... because everything journald logs (well, everything |
34 |
system, user session logs are I'm pretty sure treated separately, at |
35 |
least with persistent storage enabled, there's a note somewhere in the |
36 |
documentation that if volatile-only is set, journald throws user journals |
37 |
in with the system journals too, which implies it doesn't, with |
38 |
persistent storage) is thrown in the same log, so there's little choice |
39 |
on rotation strategy. |
40 |
|
41 |
But of course syslog-ng allows you to split the logs however you want, |
42 |
and route individual log messages to one or more logs. And those logs in |
43 |
turn can be rotated on entirely different policies. |
44 |
|
45 |
Thanks for that point too. I'm so used to thinking in terms of being |
46 |
able to split logs and setup individual logrotate policies for them, I |
47 |
hadn't even considered that implication of the common journald journals. |
48 |
|
49 |
-- |
50 |
Duncan - List replies preferred. No HTML msgs. |
51 |
"Every nonfree program has a lord, a master -- |
52 |
and if you use the program, he is your master." Richard Stallman |