From b9dc022cc2a2dfae6f5d7b4a8f6fee464877a38a Mon Sep 17 00:00:00 2001
From: Eric Covener /var/logs/errorlog.%Y-%m-%d
with log rotation at 5
+/var/log/errorlog.%Y-%m-%d
with log rotation at 5
megabytes, but 5 megabytes was reached twice in the same day, the
same log file name would be produced and log rotation would keep
writing to the same file.
This creates the files /var/logs/logfile.nnnn where nnnn is +
This creates the files /var/log/logfile.nnnn where nnnn is the system time at which the log nominally starts (this time will always be a multiple of the rotation time, so you can synchronize cron scripts with it). At the end of each rotation time (here after 24 hours) a new log is started.
This creates the files /var/logs/logfile.yyyy.mm.dd where +
This creates the files /var/log/logfile.yyyy.mm.dd where yyyy is the year, mm is the month, and dd is the day of the month. Logging will switch to a new file every day at midnight, local time.
This configuration will rotate the logfile whenever it reaches a size of 5 megabytes.
This configuration will rotate the error logfile whenever it
reaches a size of 5 megabytes, and the suffix to the logfile name
@@ -205,10 +205,10 @@ an offset.
errorlog.YYYY-mm-dd-HH_MM_SS
.
This creates the file /var/logs/logfile, truncating the file at +
This creates the file /var/log/logfile, truncating the file at startup and then truncating the file once per day. It is expected in this scenario that a separate process (such as tail) would process the file in real time.
-- 2.40.0