Hi,
Ludovic Courtès writes:
> Hello,
>
> Diego Nicola Barbato skribis:
>
>> Great! Now we can simplify the 'start' method of
>> 'syslogd-service-type'.
>
> Oh right, do you want to take care of it?
I already did: https://debbugs.gnu.org/40937
[...]
Regards,
Diego
Hello,
Diego Nicola Barbato skribis:
> Great! Now we can simplify the 'start' method of
> 'syslogd-service-type'.
Oh right, do you want to take care of it?
> I did eventually write a test script, which I've attached in case we
> want to add it to the Shepherd. I'm sorry it took so long that
Hi,
Ludovic Courtès writes:
> Hi,
>
> Ludovic Courtès skribis:
>
>> Diego Nicola Barbato skribis:
>>
From 43c9ded791ce5b480504ce3528ee34578168f90e Mon Sep 17 00:00:00 2001
>>> From: Diego Nicola Barbato
>>> Date: Tue, 7 Apr 2020 13:58:28 +0200
>>> Subject: [PATCH 1/2] service: Create log
Hi,
Ludovic Courtès skribis:
> Diego Nicola Barbato skribis:
>
>>>From 43c9ded791ce5b480504ce3528ee34578168f90e Mon Sep 17 00:00:00 2001
>> From: Diego Nicola Barbato
>> Date: Tue, 7 Apr 2020 13:58:28 +0200
>> Subject: [PATCH 1/2] service: Create log files as non-world-readable.
>>
>> *
Hi Diego,
Diego Nicola Barbato skribis:
>>From 43c9ded791ce5b480504ce3528ee34578168f90e Mon Sep 17 00:00:00 2001
> From: Diego Nicola Barbato
> Date: Tue, 7 Apr 2020 13:58:28 +0200
> Subject: [PATCH 1/2] service: Create log files as non-world-readable.
>
> * modules/shepherd/service.scm
Diego Nicola Barbato skribis:
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Diego Nicola Barbato skribis:
>>
>>> On Guix System the log files (in /var/log) generated by syslogd are
>>> currently (commit 151f3d4) world readable. They should probably only be
>>> readable by root (for the same reason
Hey,
Ludovic Courtès writes:
> Hi,
>
> Diego Nicola Barbato skribis:
>
>> On Guix System the log files (in /var/log) generated by syslogd are
>> currently (commit 151f3d4) world readable. They should probably only be
>> readable by root (for the same reason that dmesg can only be run by
>>
Hi,
Bengt Richter skribis:
> On +2020-04-07 00:07:14 +0200, Ludovic Courtès wrote:
>> Hi,
>>
>> Ludovic Courtès skribis:
>>
>> > In the meantime, the patch below fixes the syslogd problem. Also
>> > attached is a patch for the accounting database, though that one is
>> > questionable.
>>
Hi Ludo,
On +2020-04-07 00:07:14 +0200, Ludovic Courtès wrote:
> Hi,
>
> Ludovic Courtès skribis:
>
> > In the meantime, the patch below fixes the syslogd problem. Also
> > attached is a patch for the accounting database, though that one is
> > questionable.
>
> I pushed the syslog bits
Hi,
Ludovic Courtès skribis:
> In the meantime, the patch below fixes the syslogd problem. Also
> attached is a patch for the accounting database, though that one is
> questionable.
I pushed the syslog bits along with a test as commit
d7113bb655ff80a868a9e624c913f9d23e6c63ad. (I think
Hi,
Diego Nicola Barbato skribis:
> On Guix System the log files (in /var/log) generated by syslogd are
> currently (commit 151f3d4) world readable. They should probably only be
> readable by root (for the same reason that dmesg can only be run by
> root).
>
> It isn't possible to set the
Diego Nicola Barbato writes:
> Hey Guix,
>
> On Guix System the log files (in /var/log) generated by syslogd are
> currently (commit 151f3d4) world readable. They should probably only be
> readable by root (for the same reason that dmesg can only be run by
> root).
>
> It isn't possible to set
Hey Guix,
On Guix System the log files (in /var/log) generated by syslogd are
currently (commit 151f3d4) world readable. They should probably only be
readable by root (for the same reason that dmesg can only be run by
root).
It isn't possible to set the umask with fork-exec-constructor, is it?
13 matches
Mail list logo
