Rotated logs have different permissions from logs that have not yet been rotated

  • Open
  • quality assurance status badge
Details
3 participants
  • Leo Famulari
  • Ludovic Courtès
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Leo Famulari
Severity
important
Merged with

Debbugs page

L
L
Leo Famulari wrote on 10 Jul 2023 11:31
(address . bug-guix@gnu.org)
ZKxOc5C_UMPdShGX@jasmine.lan
I noticed this inconsistency:

------
$ ls -l /var/log/messages*
-rw-r----- 1 root root 112994 Jul 10 14:29 /var/log/messages
-rw-r--r-- 1 root root 8883 Jul 5 12:00 /var/log/messages.1.gz
------

This seems like a mistake.
L
L
Ludovic Courtès wrote on 6 Sep 05:20 -0700
control message for bug #64562
(address . control@debbugs.gnu.org)
87frqdynwo.fsf@gnu.org
tags 64562 + security
quit
L
L
Ludovic Courtès wrote on 6 Sep 15:17 -0700
Re: bug#64562: Rotated logs have different permissions from logs that have not yet been rotated
(name . Leo Famulari)(address . leo@famulari.name)(address . 64562@debbugs.gnu.org)
8734mcwhow.fsf@gnu.org
Hi,

Leo Famulari <leo@famulari.name> skribis:

Toggle quote (10 lines)
> I noticed this inconsistency:
>
> ------
> $ ls -l /var/log/messages*
> -rw-r----- 1 root root 112994 Jul 10 14:29 /var/log/messages
> -rw-r--r-- 1 root root 8883 Jul 5 12:00 /var/log/messages.1.gz
> ------
>
> This seems like a mistake.

Definitely. Rottlog being what it is, few people are willing to hack on
it.

Good news is that the upcoming Shepherd 1.0 has a ‘log-rotation’ that
doesn’t have this particular bug and is hopefully more hackable:


Ludo’.
M
M
Maxim Cournoyer wrote on 12 Nov 05:00 -0800
control message for bug #64562
(address . control@debbugs.gnu.org)
87a5e438un.fsf@gmail.com
severity 64562 important
quit
M
M
Maxim Cournoyer wrote on 12 Nov 05:00 -0800
(address . control@debbugs.gnu.org)
878qto38tz.fsf@gmail.com
merge 64562 57701
quit
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 64562@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 64562
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch