From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30649@debbugs.gnu.org
Subject: bug#30649: Cuirass service does not rotate its logs
Date: Thu, 01 Mar 2018 17:35:09 +0100 [thread overview]
Message-ID: <87371j69fm.fsf@gnu.org> (raw)
In-Reply-To: <20180228174823.5fec105f@scratchpost.org> (Danny Milosavljevic's message of "Wed, 28 Feb 2018 17:48:23 +0100")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> Hi Andreas,
>
> On Wed, 28 Feb 2018 15:50:39 +0100
> Andreas Enge <andreas@enge.fr> wrote:
>
>> $ 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..
>
> The simplest and best way to fix that is to make cuirass use syslog.
>
> Not every program has to have its own private logging implementation,
> log rotator, log filterting, log rate limiter, kitchen sink etc.
>
> src/cuirass/logging.scm is prepared somewhat for this possiblity[2], but it
> doesn't yet log to syslog.
>
> There are guile syslog bindings[1] and we should use them and then apply a
> two-line patch to src/cuirass/logging.scm .
Indeed. I wonder why we don’t have a Gamma package yet!
Ludo’.
next prev parent reply other threads:[~2018-03-01 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 14:50 bug#30649: Cuirass service does not rotate its logs Andreas Enge
2018-02-28 16:48 ` Danny Milosavljevic
2018-03-01 16:35 ` Ludovic Courtès [this message]
2018-03-01 16:35 ` Ludovic Courtès
2018-03-01 16:36 ` Ludovic Courtès
2018-03-01 16:43 ` Andreas Enge
2018-03-01 23:47 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87371j69fm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30649@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.