Skip to content

lock state file to prevent parallel execution#297

Closed
cgzones wants to merge 1 commit intologrotate:masterfrom
cgzones:lock
Closed

lock state file to prevent parallel execution#297
cgzones wants to merge 1 commit intologrotate:masterfrom
cgzones:lock

Conversation

@cgzones
Copy link
Member

@cgzones cgzones commented Feb 6, 2020

related to #295

@kdudka
Copy link
Member

kdudka commented Feb 13, 2020

Thank you for working on this! I will review it after the planned release of logrotate. My initial feeling is that this will need to be optional to cover the environments where the locking mechanism does not work reliably. There is some risk that the change will trigger problems even without parallel invocation.

@kdudka kdudka self-assigned this Feb 13, 2020
@cgzones cgzones marked this pull request as ready for review May 15, 2020 13:51
@cgzones cgzones force-pushed the lock branch 2 times, most recently from 4f71e98 to 5c5813c Compare May 31, 2020 09:29
Running multiple instances of logrotate on the same set of log-files
might have undesirable effects.

Add command line option --skip-state-lock to skip locking the state
file, for example if locking is unsupported or prohibited.
@kdudka
Copy link
Member

kdudka commented Jun 24, 2020

Merging now. Thank you for being patient while contributing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants