Bug#766074: systemd: users should not have to put a value greater than desired in MaxRetentionSec to avoid loss of information

[Michael Biebl]

Control: tags -1 + upstream

Hi

On Mon, 20 Oct 2014 19:33:23 +0200 (CEST) Santiago Vila
> Manual says:
> 
> MaxRetentionSec=
> 
>   The maximum time to store journal entries. This controls whether
>   journal files containing entries older then the specified time
>   span are deleted.
> 
> Ok, but what happens if the specified time is in the middle of a journal file?
> 
> It seems that current behaviour is that as far as a journal file has a
> *single* entry older than the specified time, the entire journal file
> is discarded, including entries which are older than the time limit
> but also entries which are a little bit newer than the time limit.
> 
> We could discuss whether or not this matches the documentation, but in
> my opinion this behaviour is not what one would expect.

Imho the documentation is pretty clear, saying that journal files
containing entries older then MaxRetentionSec are deleted, which can
include newer entries. But sure, the documentation can be more specific
about this aspect.

> I would expect journal files to be discarded only when all of its
> entries have expired, or, at the very minimum, manual should warn the
> user that if he/she wants to keep a whole week of logs, then the value
> of MaxRetentionSec should be greater than a week.

This really is an upstream issue, so it would be great if you can file a
bug at https://github.com/systemd/systemd/issues/new

Regards,
Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160202/97e9655f/attachment.sig>