Ah, there’s a flag for this. instead of using tail -f /var/log/file we should be using tail -F /var/log/file tail -F translates to tail –follow=name –retry as in; –follow=name: follow the name of the file instead of the file descriptor –retry: if the file is inaccessible, try again later instead of dying
ISO 8601 format should be adhered to as much as possible, since it is the closest thing there is to a standard. The ‘T’ is not enough of a stumbling block to really warrant getting rid of it. The ‘:’s are potentially killers, so those should be avoided. For the reasons mentioned in others’ answers, … Read more
In your logrotate.conf (or the equivilent logrotate.d file), change the line that says “ rotate 10 (your number may be different) to a bigger number. That will tell it to keep that many days of logs. You can make it 36500, which would last you 100 years.
As much as I wince at the suggestion, installing Cygwin is one of the very few options that you have available to you. From there, you can use logrotate.
A common issue is when you first setup a daily logrotate.d entry, it will not rotate the first day. When you use a time based rotation (daily/weekly/monthly) logrotate scribbles a date stamp of the last date it saw the file in /var/lib/logrotate/status (or /var/lib/logrotate.status on RHEL systems). The scribbled date becomes the reference date from … Read more
I believe it’s the content of the state file, which is my case is /var/lib/logrotate.status. Each file has one line, which is the date on which it was last rotated; if you run logrotate on such a date that a given file is due for rotation, given the number of days between current date and … Read more
Yes: logrotate –force $CONFIG_FILE
logrotate does not log anything by default. normally it should be in your cron somewhere, for instance: $ grep -r — ‘logrotate.conf’ /etc/cron* /etc/cron.daily/logrotate:/usr/sbin/logrotate /etc/logrotate.conf You can either run that manually to see what is wrong, or redirect the logrotate output to a file in the above cron to see what happened next day. Likely … Read more
Your understanding of copytruncate is correct, but the wording in the manpage for delaycompress is a little misleading. More properly, it should say “when some program cannot be told to immediately close it’s logfile” — for instance, if you’re using sharedscripts and the script sends a signal to the process using the log when all … Read more
If the size directive is used, logrotate will ignore the daily, weekly, monthly, and yearly directives. This is not clear in the documentation when you execute the man logrotate command. However it can be confirmed in practice, and is mentioned in some arbitrary blog posts such as this one. There is a directive called minsize … Read more