-
Notifications
You must be signed in to change notification settings - Fork 51
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
Is there a way to control how rotated log files are renamed? #172
Comments
That's not implemented so far - thanks for the proposal! |
May I ask about the advantage of this approach, as it comes with the disadvantage that the rotated files cannot be easily recognized as log files? |
First, it's pretty standard on Unix systems. For example, here on an Ubuntu machine, in So there might be people with scripts and frameworks already written for this type of naming scheme. Second, in my case specifically, I have a service writing in a log and another process monitoring the log and sending alerts when it reads certain keywords (like errors and so on). Initially, both services were reading the path of the log file from the same config file. However when I enabled log rotation, I had to split the config to tell the first service to write to Then, when I receive an alert and want to copy the log files from the server for analysis, I could select the path in the config and add a wildcard (*) at the end to include the current log and all the rotated ones (i.e. So all in all, it's not a dealbreaker, but it would make things smoother. |
Hello!
I see that rotating with
Numbers
yields files that look like this:and rotating with
NumbersDirect
yields files that look like this:However, I would like to be able to have the following (as is usual on *nix from what I could see, and this is what file_rotate does by default), is it possible?
The text was updated successfully, but these errors were encountered: