Get the logfile location while running the logrotate cron job instead… #2914
Conversation
This file contains 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
|
@icewind1991, thanks for your PR! By analyzing the history of the files in this pull request, we identified @Faldon, @bartv2 and @LukasReschke to be potential reviewers. |
… of when registering the job Signed-off-by: Robin Appelman <robin@icewind.nl>
MorrisJobke
force-pushed
the
logrotate-logfile
branch
from
d2db9bc
to
54f96e5
Compare
|
Rebased to fix autoloader check failure. |
rullzer
approved these changes
Jan 6, 2017
MorrisJobke
added
4. to release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
… of when registering the job
@tflidd can you check if this fixes the problem with logrotate and moving the data directory