Hello Jan,
----- Original Message -----
From: Jan Kaluza <jkaluza(a)redhat.com>
Subject: Re: logrotate(8) and copytruncate as default
I think difference between systemd and logrotate in this case is that
logrotate is not owner of the logs it rotates. It has no control of writing
to them. I haven't checked that journald code, but journald definitely
controls the log and is (correct me if I'm wrong) the only application writing to
it.
Therefore it's not problem for journald to just write some line to log,
check that the log is too big and rotate it. It doesn't have to do any locking
to stop writing, it just does not write any data there during rotation.
Ah, yep true. In my head I kept thinking application is writing to a file.
Right, locking wouldn't be required if journald is the sole writer to a file.
Thank you!
---
Regards
-Prasad
http://feedmug.com