Recent changes to wiki

Discussion for Home page

Howard Spindel — Mon, 13 Feb 2023 07:24:50 -0000

For a test run, use logrotate -d <configfile></configfile>

That will give you debugging output about what logrotate would do if it ran. No files will be affected.

Discussion for Home page

Howard Spindel — Mon, 13 Feb 2023 03:15:50 -0000

Here is my config file:

compress
nosmtpssl
smtpfrom howard@sci1.com
smtpport 25
smtpserver mail.sci1.com
ifempty
missingok

e:\FastvueSyslog\dhcp2.sci1.com\dhcp2.sci1.com.log
{
rotate 5
weekly
mail howard@sci1.com
}

Pretty simple. When I run logrotate, I get an error:

logrotate: Unknown directive e:\FastvueSyslog\dhcp2.sci1.com\dhcp2.sci1.com.log

What am I doing wrong?

Discussion for LogRotate page

V@no — Sun, 14 Nov 2021 15:50:28 -0000

We have to manually create scheduling tasks for this to work, correct?
Also, what is logrotate.exe.config file in the root of installation directory?

Discussion for Home page

Marcos — Mon, 11 Aug 2014 21:21:42 -0000

Hi all (sorry for my english), I would like to know how to make a folder logs rotate every day, and compress the content (do not want to remove)
This is the configuration file content:

compress

C:\Documents and Settings\synchrot\Desktop\BackupsLogsPrueba {
rotate 5
daily
prerotate
@echo off
echo This is a test
echo parameter pass %1
VER | TIME > TEMP.BAT
ECHO SET TIME=%%3>CURRENT.BAT
DEL TEMP.BAT
DEL CURRENT.BAT
ECHO It's %TIME% now

endscript

}

I Do not know how to test run, and if it is well configured.
Could you please help me?

Thanks.

LogRotate modified by Ken Salter

Ken Salter — Fri, 24 May 2013 14:14:08 -0000

--- v6
+++ v7
@@ -86,7 +86,8 @@
     endscript
 }

-"c:\program files\application\*" {
+"c:\program files\application\*\*" {
+    # this section matches all files in all subfolders of c:\program files\application
     monthly
     rotate 2
     olddir "c:\program files\application\oldlogs"

WikiPage LogRotate modified by Ken Salter

Ken Salter — Tue, 30 Oct 2012 21:00:52 -0000

--- v5
+++ v6
@@ -245,6 +245,10 @@
 
 Do not use shred when deleting old log files. See also **shred**.
 
+**nosmtpssl**
+
+Disables using SSL to send email.  See also **smtpssl**.
+
 **notifempty**
 
 Do not rotate the log if it is empty (this overrides the **ifempty** option).
@@ -292,6 +296,30 @@
 **start** *count*
 
 This is the number to use as the base for rotation. For example, if you specify 0, the logs will be created with a .0 extension as they are rotated from the original log files. If you specify 9, log files will be created with a .9, skipping 0-8. Files will still be rotated the number of times specified with the **count** directive.
+
+**smtpfrom** *fromaddress*
+
+Sets the "from" email address for emails that are sent from **logwatch**.  The default value is "logwatch@computername" where computername is the name of the computer that **logwatch** is running on.
+
+**smtpport** *port*
+
+Sets the TCP/IP port number **logwatch** will connect to when sending email.  The default is 25.  Setting this value to 0 will disable email sending.
+
+**smtpserver** *hostname*
+
+Sets the hostname or IP address of the target SMTP server for sending emails.  Setting this directive with no hostname defined will disable email.
+
+**smtpssl**
+
+Emails sent from **logwatch** will be sent using SSL.  The target mail server must support SSL.  This is turned off by default.  See also **nosmtpssl**.
+
+**smtpuser** *username*
+
+Mail servers that require SMTP authentication have to be sent a valid username and password.  This directive sets the username that will be sent.  By default, no SMTP authentication will be attempted.  Setting this value to something other than blank will cause SMTP authentication to be performed.
+
+**smtpuserpwd** *password*
+
+Mail servers that require SMTP authentication have to be sent a valid username and password.  This directive sets the password that will be sent.  By default, no SMTP authentication will be attempted.  **Note that the password is stored in clear text in the configuration file.**
 
 **tabooext** *[+] list*

WikiPage LogRotate modified by Ken Salter

Ken Salter — Tue, 30 Oct 2012 15:41:44 -0000

--- v4
+++ v5
@@ -29,9 +29,9 @@
 
 Tells **logrotate** to force the rotation, even if it doesn't think this is necessary. Sometimes this is useful after adding new entries to a **logrotate** config file, or if old log files have been removed by hand, as the new files will be created, and logging will continue correctly.
 
-**-m, --mail **
-
-Tells **logrotate** which command to use when mailing logs. This command should accept two arguments: 1) the subject of the message, and 2) the recipient. The command must then read a message on standard input and mail it to the recipient. The default mail command is /bin/mail -s.
+**-m, --mail **
+
+Tells **logrotate** which command to use when mailing logs. This command should accept two arguments: 1) the subject of the message, and 2) the recipient. The command must then read a message on standard input and mail it to the recipient. The default mail command is /bin/mail -s.
 
 *The -m argument has been deprecated.  Email settings are now controlled with new directives in the configuruation files.*

WikiPage LogRotate modified by Ken Salter

Ken Salter — Tue, 30 Oct 2012 15:30:47 -0000

--- v3
+++ v4
@@ -12,7 +12,7 @@
 -----------
 **logrotate** is designed to ease administration of systems that generate large numbers of log files. It allows automatic rotation, compression, removal, and mailing of log files. Each log file may be handled daily, weekly, monthly, or when it grows too large.
 
-Normally, **logrotate** is run as a daily scheduled task. It will not modify a log multiple times in one day unless the criteria for that log is based on the log's size and **logrotate** is being run multiple times each day, or unless the -f or -force option is used.
+Normally, **logrotate** is run as a daily scheduled task. It will not modify a log multiple times in one day unless the criteria for that log is based on the log's size and **logrotate** is being run multiple times each day, or unless the **-f** or **-force** option is used.
 
 Any number of config files may be given on the command line. Later config files may override the options given in earlier files, so the order in which the **logrotate** config files are listed is important. Normally, a single config file which includes any other config files which are needed should be used. See below for more information on how to use the include directive to accomplish this. If a directory is given on the command line, every file in that directory is used as a config file.
 
@@ -174,6 +174,7 @@
 Reads the file given as an argument as if it was included inline where the include directive appears. If a directory is given, most of the files in that directory are read in alphabetic order before processing of the including file continues. The only files which are ignored are files which are not regular files (such as directories and named pipes) and files whose names end with one of the taboo extensions, as specified by the **tabooext** directive. The include directive may not appear inside a log file definition.
 
 **mail** *address*
+
 When a log is rotated out-of-existence, it is mailed to address. If no mail should be generated by a particular log, the **nomail** directive may be used.  Note that this directive has no effect unless the **smtpserver** directive is specified (along with any other smtp directives required for email sending to work.)
 
 **mailfirst**
@@ -262,7 +263,7 @@
 
 **firstaction/endscript**
 
-The lines between firstaction and endscript (both of which must appear on lines by themselves) are executed (using /bin/sh) once before all log files that match the wildcarded pattern are rotated, before prerotate script is run and only if at least one log will actually be rotated. These directives may only appear inside a log file definition. Whole pattern is passed to the script as first argument. If the script exits with error, no further processing is done. See also lastaction.
+The lines between **firstaction** and **endscript** (both of which must appear on lines by themselves) are executed (using cmd) once before all log files that match the wildcarded pattern are rotated, before **prerotate** script is run and only if at least one log will actually be rotated. These directives may only appear inside a log file definition. Whole pattern is passed to the script as first argument. If the script exits with error, no further processing is done. See also **lastaction**.
 
 **lastaction/endscript**
 
@@ -294,7 +295,7 @@
 
 **tabooext** *[+] list*
 
-The current taboo extension list is changed (see the **include** directive for information on the taboo extensions). If a + precedes the list of extensions, the current taboo extension list is augmented, otherwise it is replaced. At startup, the taboo extension list contains .swp.
+The current taboo extension list is changed (see the **include** directive for information on the taboo extensions). If a + precedes the list of extensions, the current taboo extension list is augmented, otherwise it is replaced. The list of extensions is seprated by spaces.  At startup, the taboo extension list contains .swp.
 
 **weekly**

WikiPage Home modified by Ken Salter

Ken Salter — Tue, 30 Oct 2012 13:45:05 -0000

--- v1
+++ v2
@@ -1,8 +1,8 @@
-Welcome to your wiki!
+Welcome to the LogRotateWin Wiki!
 
-This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: [SamplePage].
+The following pages have been created:
 
-The wiki uses [Markdown](/p/logrotatewin/wiki/markdown_syntax/) syntax.
+[LogRotate] - A page in a *man* style containing all information needed to configure and run **logrotate**.
 
 [[project_admins]]
 [[download_button]]

WikiPage LogRotate modified by Ken Salter

Ken Salter — Tue, 30 Oct 2012 13:41:19 -0000

--- v2
+++ v3
@@ -22,22 +22,29 @@
 -------
 
 **-d**
+
 Turns on debug mode and implies -v. In debug mode, no changes will be made to the logs or to the **logrotate** state file.
 
 **-f, --force**
+
 Tells **logrotate** to force the rotation, even if it doesn't think this is necessary. Sometimes this is useful after adding new entries to a **logrotate** config file, or if old log files have been removed by hand, as the new files will be created, and logging will continue correctly.
 
 **-m, --mail **
+
 Tells **logrotate** which command to use when mailing logs. This command should accept two arguments: 1) the subject of the message, and 2) the recipient. The command must then read a message on standard input and mail it to the recipient. The default mail command is /bin/mail -s.
+
 *The -m argument has been deprecated.  Email settings are now controlled with new directives in the configuruation files.*
 
 **-s, --state **
+
 Tells **logrotate** to use an alternate state file. This is useful if **logrotate** is being run as a different user for various sets of log files. The default state file is logrotate.status located in the folder where **logrotate** is installed.
 
 **--usage**
+
 Prints a short usage message.
 
 **-v, --verbose**
+
 Turns on verbose mode.
 
 Configuration File