Allow dot in cron.update to re-scan whole directory #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's kind of tedious if one has to explicitely name every changed file, particularly in case of package installs or uninstalls. And having uninstalled packages emit error messages for up to an hour is suboptimal as well. It would be better if package managers could help us here, by triggering a re-scan of the whole directory afer installs or uninstalls.
The documentation also failed to mention
/etc/cron.d/cron.updatebefore, causing me to assume that/var/spool/cron/crontabs/cron.updatecould somehow be used to trigger a re-scan of/etc/cron.das well. It should be clearer now.Code is untested, but the change looks simple enough.