emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#30649: closed (shepherd services with #:log-file o


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#30649: closed (shepherd services with #:log-file overwrite their log file)
Date: Fri, 02 Mar 2018 13:01:02 +0000

Your message dated Fri, 02 Mar 2018 00:47:55 +0100
with message-id <address@hidden>
and subject line Re: bug#30649: Cuirass service does not rotate its logs
has caused the debbugs.gnu.org bug report #30649,
regarding shepherd services with #:log-file overwrite their log file
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
30649: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=30649
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Cuirass service does not rotate its logs Date: Wed, 28 Feb 2018 15:50:39 +0100 User-agent: Mutt/1.9.3 (2018-01-21)
Hello,

while testing the cuirass service on bayfront, I see the following:

$ ll /var/log/c*
-rw-r--r-- 1 root root 2003521 Feb 28 15:38 /var/log/cuirass.log

I am sure this 2MB file was about 14MB big this morning, and indeed
any information dating from before this morning, when I rebooted the
machine and thus restarted the service, has gone.

Notice also that there are no numbered files cuirass.log.1 etc..

Andreas




--- End Message ---
--- Begin Message --- Subject: Re: bug#30649: Cuirass service does not rotate its logs Date: Fri, 02 Mar 2018 00:47:55 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)
Andreas Enge <address@hidden> skribis:

> On Thu, Mar 01, 2018 at 05:35:54PM +0100, Ludovic Courtès wrote:
>> The cuirass service in GuixSD explicitly extends rottlog so that this
>> file is rotated on a weekly basis.  Perhaps you just need to wait a
>> little longer?
>
> The problem is not that the file grows too large.
>
> The problem was that after rebooting the server, the file was *replaced*
> with newly written content. Maybe the problem is not rotation, but opening
> a file in "write" instead of "append" mode...

Oh indeed, that’s a different thing.

This is fixed by Shepherd commit
7b4c88bac70f0bad82ef70fd5b682a49bc227478, thanks!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]