On 08/09/19 16:48, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the logrotate package:
#691407: logrotate(8) does not mention all reasons for ignoring included files
It has been closed by Christian Göttsche .
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Christian Göttsche
by
replying to this email.
Subject:
Re: logrotate(8) does not mention all reasons for ignoring included files
From:
Christian Göttsche
Date:
08/09/19 17:45 +0200
To:
691407-d...@bugs.debian.org
To:
691407-d...@bugs.debian.org
Closing due to no response.
No response due to not being copied on the email in question!
In the BTS, I see that on Wed, 22 Aug 2018 22:54:02 +0200, Christian
Göttsche apparently wrote:
Control: tags -1 moreinfo unreproducible
Hi,
by
some unspecified "bad" file modes, which include being group writeable.
do you mean configuration files or log files?
In my tests logrotate does rotate logs which are group writeable and
errors out when a configuration file has insecure permissions.
I don't remember filing this bug seven years ago, but the section of the man
page quoted in the original report was clearly referring to configuration
files. You have reproduced the error, which was a result of a requirement
which I could not find in the the man page. If this bug is unreproducible,
does that mean you were able to find where in the man page this is documented?
Having left cron to run overnight with an erroneous logrotate.d file I see
that an error is now reported without needing to resort to adding "-v" to
various scripts:
"error: Ignoring vsftpd because of bad file mode - must be 0644 or 0444."
and it now states what the file mode requirements are, which it did not
before. As a result it would probably be reasonable to downgrade this bug to
minor severity.
Previously no error was reported when the script was run by cron, when "-v"
was added to logrotate the error message given did not state what was wrong
with the file mode and this requirement is not mentioned in the man page.
This made it difficult to work out why logrotate was not working.
Regards,
Roger
