From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ulogd: fix logrotate file, add conf_files
Date: Tue, 02 Nov 2021 04:57:16 +0100 [thread overview]
Message-ID: <20211102035716.HJJJia7mT5LT_qy3nw7AVOCQMzG1jj4EyJaKCx0IJxU@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: 925 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/pull/33847#issuecomment-957045521
Comment:
> Options for how include doing it in the runit service or the package INSTALL script.
If we use the runit or INSTALL script to create the log files, there will be log files such as `/var/log/ulogd.pcap` that will be created even though they may not be used. There are also other log files specified in `/etc/ulogd.conf` which will be left with incorrect ownership/permissions if enabled.
How about instead we move the logs to `/var/log/ulogd/` and set the ownership to `root:root` or `root:adm` and mode to `750` to restrict access? This will require modification of `/etc/ulogd.conf`. The logrotate directive `create 640 _ulogd adm` can be removed and the log files will be owned by `root:root`. The logrotate file can then be configured to rotate every file `/var/log/ulogd/`.
next prev parent reply other threads:[~2021-11-02 3:57 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
2021-11-01 3:12 ` ericonr
2021-11-01 6:13 ` CameronNemo
2021-11-02 2:37 ` amak79
2021-11-02 3:57 ` amak79 [this message]
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=20211102035716.HJJJia7mT5LT_qy3nw7AVOCQMzG1jj4EyJaKCx0IJxU@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).