-
Couldn't load subscription status.
- Fork 11
fix: logrotate error #1005
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
fix: logrotate error #1005
Conversation
WalkthroughThe pull request introduces a modification to the log rotation configuration for the Unraid API. The change involves updating the log rotation setup script to include a new directive specifying the user and group under which log rotation should be performed. The Changes
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms (2)
🔇 Additional comments (4)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
This plugin has been deployed to Cloudflare R2 and is available for testing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Fixes:
error: skipping "/var/log/unraid-api/unraid-api.log" because parent =
directory has insecure permissions (It's world writable or writable by =
group which is not "root") Set "su" directive in config file to =
tell logrotate which user/group should be used for rotation.
Improvements
No longer indents logrotate.conf for unraid-api
Summary by CodeRabbit