From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ulogd: fix logrotate file, add conf_files
Date: Mon, 01 Nov 2021 01:45:28 +0100 [thread overview]
Message-ID: <20211101004528.ssFiylwNK8WGzBbOHvrWDZpgIddpyRLxIM1V2rrdPpU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33847@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/pull/33847#issuecomment-955828695
Comment:
I noticed when ulogd is started for the first time, `/var/log/ulogd.log` is created with `root:root` ownership and `644` mode. When the log file is rotated, a new log file is created with `_ulogd:adm` ownership and `640` mode as expected. After 4 rotations the ownership and mode will be same for all log files.
Should we make the initial and rotated log files have the same ownership and mode? My concern is that the initial log file is world readable. I fixed it by manually changing the ownership and mode to that of the rotated log files.
next prev parent reply other threads:[~2021-11-01 0:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 12:50 [PR PATCH] ulogd: fix logrotate file amak79
2021-10-31 13:00 ` amak79
2021-10-31 13:09 ` amak79
2021-10-31 13:09 ` [PR PATCH] [Updated] " amak79
2021-10-31 23:03 ` [PR REVIEW] ulogd: fix logrotate file, add conf_files ericonr
2021-10-31 23:12 ` [PR PATCH] [Updated] " amak79
2021-10-31 23:15 ` [PR REVIEW] " amak79
2021-11-01 0:45 ` amak79 [this message]
2021-11-01 3:12 ` ericonr
2021-11-01 6:13 ` CameronNemo
2021-11-02 2:37 ` amak79
2021-11-02 3:57 ` amak79
2021-11-02 4:02 ` amak79
2021-11-02 4:15 ` [PR PATCH] [Updated] " amak79
2021-11-02 4:21 ` amak79
2021-11-03 2:26 ` [PR REVIEW] ulogd: move logs to subdir, update " CameronNemo
2021-11-03 2:26 ` CameronNemo
2021-11-03 2:26 ` CameronNemo
2021-11-03 2:27 ` CameronNemo
2021-11-03 2:50 ` [PR PATCH] [Updated] " amak79
2021-11-03 2:56 ` [PR REVIEW] " amak79
2021-11-03 2:57 ` amak79
2021-11-03 3:03 ` CameronNemo
2021-11-14 7:07 ` [PR PATCH] [Merged]: " ericonr
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=20211101004528.ssFiylwNK8WGzBbOHvrWDZpgIddpyRLxIM1V2rrdPpU@z \
--to=amak79@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).