Skip to content

ncm-altlogrotate: global logrotate config fails to be modified in some cases #1813

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

StephaneGerardVUB
Copy link

See issue #1657 for more details

wpoely86
wpoely86 previously approved these changes Feb 27, 2025
@wpoely86
Copy link
Member

This fixes #1657

Copy link
Contributor

@ned21 ned21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry if this sounds a bit paranoid but a commit message which only references a ticket in the bug tracking system could lead to problems in the future since there's no guarantee we'll be able to migrate the bug data along with git repository to pastures new. Could you please provide a full explanation of the change being made in the commit log so it documents the change alongside the code?

…when reaching the if of line 138, and if we don't check the value of $overallglobal (that is switched to 1 in case of an entry named 'global'), then the block of code modifying the global configuration file will be skipped
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

ncm-altlogrotate: with only the global entry, and no entries marked as global, main configfifle is not edited
4 participants