-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logrotate config: global options cause foreign files to be owned #2110
Labels
Milestone
Comments
ghost
added
bug
Indicates an unexpected problem or unintended behavior
packaging
component: contrib
labels
Sep 14, 2021
ghost
added this to the 3.1.0 milestone
Sep 14, 2021
ghost
self-assigned this
Sep 14, 2021
ghost
pushed a commit
that referenced
this issue
Sep 14, 2021
The packaged configuration for logrotate falsely contained options applying to other programs' log files. This caused wrong ownerships of log files. This issues is corrected, but the ownership of affected log files may need to be changed manually. To find affected files, you may use: ```bash sudo find /var/log/ -user intelmq ! -path \*intelmq\* ``` fixes #2110
ghost
mentioned this issue
Sep 14, 2021
ghost
pushed a commit
that referenced
this issue
Sep 14, 2021
The packaged configuration for logrotate falsely contained options applying to other programs' log files. This caused wrong ownerships of log files. This issues is corrected, but the ownership of affected log files may need to be changed manually. To find affected files, you may use: ```bash sudo find /var/log/ -user intelmq ! -path \*intelmq\* ``` fixes #2110
ghost
pushed a commit
that referenced
this issue
Sep 14, 2021
The packaged configuration for logrotate falsely contained options applying to other programs' log files. This caused wrong ownerships of log files. This issues is corrected, but the ownership of affected log files may need to be changed manually. To find affected files, you may use: ```bash sudo find /var/log/ -user intelmq ! -path \*intelmq\* ``` fixes #2110
ghost
pushed a commit
that referenced
this issue
Sep 14, 2021
The packaged configuration for logrotate falsely contained options applying to other programs' log files. This caused wrong ownerships of log files. This issues is corrected, but the ownership of affected log files may need to be changed manually. To find affected files, you may use: ```bash sudo find /var/log/ -user intelmq ! -path \*intelmq\* ``` fixes #2110
ghost
pushed a commit
that referenced
this issue
Sep 16, 2021
The packaged configuration for logrotate falsely contained options applying to other programs' log files. This caused wrong ownerships of log files. This issues is corrected, but the ownership of affected log files may need to be changed manually. To find affected files, you may use: ```bash sudo find /var/log/ -user intelmq ! -path \*intelmq\* ``` fixes #2110
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0 participants
These options:
intelmq/contrib/logrotate/intelmq
Lines 1 to 3 in e3cfac7
apply to all files handled by logrotate, not just the intelmq-ones. The effect is, that many unrelated logfiles get owned by intelmq.
The text was updated successfully, but these errors were encountered: