From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: rottlog: rotate messages daily.
Date: Wed, 07 Sep 2016 11:52:42 +0200 [thread overview]
Message-ID: <87k2eoox3p.fsf@gnu.org> (raw)
In-Reply-To: <87d1lfziew.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Thu, 11 Aug 2016 12:52:55 +0200")
Hi!
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> Using the attached patch and the configuration below, rottlog
> actually rotates /var/log/messages daily.
Woohoo!
> From c7fc570327faeb50503494b370a2f5ab21d4049b Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <janneke@gnu.org>
> Date: Sat, 18 Jun 2016 22:37:48 +0200
> Subject: [PATCH] gnu: rottlog: rotate messages daily.
>
> * gnu/packages/admin.scm (rottlog): Set packdir in etc/rc; fixes rotating.
> Rename weekly to daily; rotates /var/log/messages daily.
I split it in several patches and pushed part of this.
‘rottlog’ was looking for config files in OUT/etc, which made it
impossible for people to configure it. So in commit
268ad34e0eadf8a015798b5c5587aad65b9f3a61 I changed it to look for
configuration files in /etc/rottlog.
Consequently, running “rottlog” alone won’t work; one has to provide
/etc/rottlog/{rc,daily} first. We should have a GuixSD service that
does that.
Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-09-07 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 10:52 [PATCH] gnu: rottlog: rotate messages daily Jan Nieuwenhuizen
2016-09-07 9:52 ` Ludovic Courtès [this message]
2016-09-07 12:32 ` Jan Nieuwenhuizen
2016-09-09 5:26 ` Jan Nieuwenhuizen
2016-09-11 13:30 ` Ludovic Courtès
2016-09-12 21:35 ` Jan Nieuwenhuizen
2016-09-13 21:41 ` Ludovic Courtès
2016-09-14 18:30 ` Jan Nieuwenhuizen
2016-09-20 5:15 ` Ludovic Courtès
2016-09-20 20:47 ` Jan Nieuwenhuizen
2016-09-21 15:32 ` Ludovic Courtès
2016-09-22 20:51 ` Jan Nieuwenhuizen
2016-10-02 22:39 ` 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=87k2eoox3p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.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.