From 7413ff332c3edb5d19a58e11195aea6e5e51106b Mon Sep 17 00:00:00 2001 From: Asif Bacchus Date: Sun, 24 May 2020 03:44:46 -0600 Subject: [PATCH] --- 7.1.1-Logfile-Group-file.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/7.1.1-Logfile-Group-file.md b/7.1.1-Logfile-Group-file.md index 15b033e..635c590 100644 --- a/7.1.1-Logfile-Group-file.md +++ b/7.1.1-Logfile-Group-file.md @@ -1,6 +1,6 @@ # logfile-group file (/etc/logwatch/conf/logfiles/backup.conf) -## Log file location +## log file location Update this as needed to point to the location and name of the log file generated by the backup script. Remember, by default, the log file is created in the same directory as the script itself. @@ -16,7 +16,7 @@ LogFile = /var/log/backup.log ... ``` -## Archive location and name format +## archive location and name format If you want Logwatch to process old (archived) log files generated by something like *logrotate*, then you have to specify the location and file name format of those files. I've included the generalized compressed format of such rotated files as the default in the script. Suppose you store your log files in the recommended location (*/var/log/*) and are using *Logrotate* with compression enabled, the archive line would look like: @@ -30,7 +30,7 @@ This would tell Logwatch, when the archive option is set to true, that your *bac **Note: This line is totally optional and only used if you set the archive option in Logwatch to true (default). You can comment/delete this line if you wish.** -## External script for timestamp processing +## external script for timestamp processing Since the log file uses a non-standard (according to Logwatch) method of datestamping, a custom filter had to be created. See [page 7.1.4](https://git.asifbacchus.app/asif/MailcowBackup/wiki/7.1.4-Timestamp-processing) of this wiki more information.