Jan Nieuwenhuizen skribis:
> From f4b03963d6ba6a232fca4ed749695423547d0ad5 Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen
> Date: Thu, 8 Sep 2016 01:20:43 +0200
> Subject: [PATCH] gnu: services: add rottlog.
>
> * gnu/services/admin.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add i
Ludovic Courtès writes:
Hi!
> The ‘rottlog-configuration’ is actually a macro. So at every call site
> where a default value is used, the default value code is duplicated,
> leading to code bloat if that default value is a big expression.
Ah, ok.
>> I'm not sure if we should export the %defaul
Hello!
Jan Nieuwenhuizen skribis:
> Ludovic Courtès writes:
[...]
>>> + (jobs rottlog-jobs ; list of
>>> +(default
>>> + (list #~(job
>>> + '(next-hour '(0))
>>> + (lambda ()
>>> + (system (s
Ludovic Courtès writes:
Hi Ludo,!
> The current ‘tweak-rc-weekly’ phase “fixes a bug” in etc/weekly, but I
> don’t think we should do customization in the package itself. Instead,
> it would be more appropriate to generate/provide the configuration files
> that we need, without further modifying
Hello Jan!
Jan Nieuwenhuizen skribis:
> Ludovic Courtès writes:
>
>> I would add /var/log/{secure,shepherd.log}, but weekly is probably
>> enough.
>
> Ok. I implemented this by changing the rottlog package that already
> modifies etc/weekly.
The current ‘tweak-rc-weekly’ phase “fixes a bug” in
Ludovic Courtès writes:
> I would add /var/log/{secure,shepherd.log}, but weekly is probably
> enough.
Ok. I implemented this by changing the rottlog package that already
modifies etc/weekly. I'm not sure if sending SIGHUP to syslog is
ok for shepherd.log or that would need to be a kill 1? See
Halo!
Jan Nieuwenhuizen skribis:
> Ludovic Courtès writes:
[...]
>> The configuration probably contain something like an list of name/config
>> pairs as well as an ‘rc’ file, along these lines:
>>
>> (rottlog-configuration
>> (periods `(("weekly" . ,(file-append rottlog "/etc/weekly))
>>
Ludovic Courtès writes:
Hi!
>> I made an attempt at a simple version of such a service. Its currently
>> just copying rc and writing a daily/weekly, find a working example
>> attached.
>
> Great! Comments below.
Thanks...new patch attached!
> It’s possible to make it so that users only need t
Hello!
Jan Nieuwenhuizen skribis:
>>> ‘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, run
Jan Nieuwenhuizen writes:
Hi!
>> ‘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 “rottl
Ludovic Courtès writes:
>> Using the attached patch and the configuration below, rottlog
>> actually rotates /var/log/messages daily.
>
> Woohoo!
:-)
Yeah, made me quite happy too.
>> * gnu/packages/admin.scm (rottlog): Set packdir in etc/rc; fixes rotating.
>> Rename weekly to daily; rotates /
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
updatedb-job))
...
))
--8<---cut here---end--->8---
>From c7fc570327faeb50503494b370a2f5ab21d4049b Mon Sep 17 00:00:00 2001
From: Jan Nieuwenhuizen
Date: Sat, 18 Jun 2016 22:37:48 +0200
Subject: [PATCH] gnu: rottlog: rotate messages
13 matches
Mail list logo
