Logrotateの設定
出典: Asterisk works Wiki
Redhat系のlinuxではほぼ標準でインストールされているログファイルを時間とともに切り替えていくためのプログラム。
設定
設定するには/etc/logrotate.confと/etc/logrotate.d/の設定ファイル群で行う。
- /etc/logrotate.conf
- logrotateのデフォルトの設定を行っている。
- /etc/logrotate.d/の設定ファイル群
- 各アプリケーション毎のローテーションの設定を行っている
設定の構文
次の設定はデフォルトのApache HTTP Serverのログファイルをローテーションする設定です。
/usr/local/apache/logs/access_log /usr/local/apache/logs/error_log {
missingok
sharedscripts ←複数のログファイルを指定しているので記述する必要があります。
postrotate
/bin/kill -HUP `cat /usr/local/apache2/logs/httpd.pid`
endscript
}
上記例からわかるように次のような構造が1単位です。
ローテーションするファイルパス {
設定
}
設定に使える値は次のようなものがあります。
| パラメータ | 説明 |
|---|---|
| compress | Old versions of log files are compressed with gzip by default. See also nocompress. |
| compresscmd | Specifies which command to use to compress log files. The default is gzip. See also compress. |
| uncompresscmd | Specifies which command to use to uncompress log files. The default is gunzip. |
| compressext | Specifies which extension to use on compressed log-files, if compression is enabled. The default fol-lows that of the configured compression command. |
| compressoptions | Command line options may be passed to the compres-sion program, if one is in use. The default, for gzip, is "-9" (maximum compression). |
| copy | Make a copy of the log file, but don’t change the original at all. This option can be used, for
instance, to make a snapshot of the current log file, or when some other utility needs to truncate or pare the file. When this option is used, the create option will have no effect, as the old log file stays in place. |
| copytruncate | Truncate the original log file in place after cre-ating a copy, instead of moving the old log file
and optionally creating a new one, It can be used when some program can not be told to close its log- file and thus might continue writing (appending) to the previous log file forever. Note that there is a very small time slice between copying the file and truncating it, so some logging data might be lost. When this option is used, the create option will have no effect, as the old log file stays in place. |
| create mode owner group | Immediately after rotation (before the postrotate script is run) the log file is created (with the
same name as the log file just rotated). mode specifies the mode for the log file in octal (the same as chmod(2)), owner specifies the user name who will own the log file, and group specifies the group the log file will belong to. Any of the log file attributes may be omitted, in which case those attributes for the new file will use the same val-ues as the original log file for the omitted attributes. This option can be disabled using the nocreate option. |
| daily | Log files are rotated every day. |
| dateext | Archive old versions of log files adding a daily extension like YYYYMMDD instead of simply adding a
number. |
| delaycompress | Postpone compression of the previous log file to the next rotation cycle. This has only effect when
used in combination with compress. It can be used when some program can not be told to close its log- file and thus might continue writing to the previ-ous log file for some time. |
| extension ext | Log files with ext extension can keep it after the rotation. If compression is used, the compres-
sion extension (normally .gz) appears after ext. For example you have a logfile named mylog.foo and want to rotate it to mylog.1.foo.gz instead of mylog.foo.1.gz. |
| ifempty | Rotate the log file even if it is empty, overiding the notifempty option (ifempty is the default). |
| include file_or_directory | 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 of 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. |
| mailfirst | When using the mail command, mail the just-rotated file, instead of the about-to-expire file. |
| maillast | When using the mail command, mail the about-to-expire file, instead of the just-rotated file (this
is the default). |
| maxage count | Remove rotated logs older than <count> days. The age is only checked if the logfile is to be
rotated. The files are mailed to the configured address if maillast and mail are configured. |
| minsize size | Log files are rotated when they grow bigger then size bytes, but not before the additionally speci-
fied time interval (daily, weekly, monthly, or yearly). The related size option is similar except that it is mutually exclusive with the time inter-val options, and it causes log files to be rotated without regard for the last rotation time. When minsize is used, both the size and timestamp of a log file are considered. |
| missingok | If the log file is missing, go on to the next one without issuing an error message. See also
nomissingok. |
| monthly | Log files are rotated the first time logrotate is run in a month (this is normally on the first day
of the month). |
| nocompress | Old versions of log files are not compressed with gzip. See also compress. |
| nocopy | Do not copy the original log file and leave it in place. (this overrides the copy option). |
| nocopytruncate | Do not truncate the original log file in place after creating a copy (this overrides the copytrun-
cate option). |
| nocreate | New log files are not created (this overrides the create option). |
| nodelaycompress | Do not postpone compression of the previous log file to the next rotation cycle (this overrides the
delaycompress option). |
| nodateext | Do not archive old versions of log files with date extension (this overrides the dateext option). |
| nomail | Don’t mail old log files to any address. |
| nomissingok | If a log file does not exist, issue an error. This is the default. |
| noolddir | Logs are rotated in the same directory the log nor-mally resides in (this overrides the olddir
option). nosharedscripts Run prerotate and postrotate scripts for every log file which is rotated (this is the default, and overrides the sharedscripts option). If the scripts exit with error, the remaining actions will not be executed for the affected log only. |
| noshred | Do not use shred when deleting old log files. See also shred. |
| notifempty | Do not rotate the log if it is empty (this over-rides the ifempty option). |
| olddir directory | Logs are moved into directory for rotation. The directory must be on the same physical device as
the log file being rotated, and is assumed to be relative to the directory holding the log file unless an absolute path name is specified. When this option is used all old versions of the log end up in directory. This option may be overriden by the noolddir option. |
| postrotate/endscript | The lines between postrotate and endscript (both of which must appear on lines by themselves) are exe-
cuted after the log file is rotated. These direc-tives may only appear inside of a log file defini- tion. See prerotate as well. See sharedscripts and nosharedscripts for error handling. |
| prerotate/endscript | The lines between prerotate and endscript (both of which must appear on lines by themselves) are exe-
cuted before the log file is rotated and only if the log will actually be rotated. These directives may only appear inside of a log file definition. See postrotate as well. See sharedscripts and nosharedscripts for error handling. |
| firstaction/endscript | The lines between firstaction and endscript (both of which must appear on lines by themselves) are
executed 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 of a log file definition. If the script exits with error, no further processing is done. See lastaction as well. |
| lastaction/endscript | The lines between lastaction and endscript (both of which must appear on lines by themselves) are exe-
cuted once after all log files that match the wild-carded pattern are rotated, after postrotate script is run and only if at least one log is rotated. These directives may only appear inside of a log file definition. If the script exits with error,just an error message is shown (as this is the last action). See firstaction as well. |
| rotate count | Log files are rotated <count> times before being removed or mailed to the address specified in a
mail directive. If count is 0, old versions are removed rather then rotated. |
| size size | Log files are rotated when they grow bigger then size bytes. If size is followed by M, the size if
assumed to be in megabytes. If the k is used, the size is in kilobytes. So size 100, size 100k, and size 100M are all valid. |
| sharedscripts | Normally, prescript and postscript scripts are run for each log which is rotated, meaning that a sin-
gle script may be run multiple times for log file entries which match multiple files (such as the /var/log/news/* example). If sharedscript is speci-fied, the scripts are only run once, no matter how many logs match the wildcarded pattern. However, if none of the logs in the pattern require rotat- ing, the scripts will not be run at all. If the scripts exit with error, the remaining actions will not be executed for any logs. This option overrides the nosharedscripts option and implies create option. shred Delete log files using shred -u instead of unlink(). This should ensure that logs are not readable after their scheduled deletion; this is off by default. See also noshred. |
| shredcycles count | Asks GNU shred to overwite log files count times before deletion. Without this option, shred’s
default will be used. |
| 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. |
| 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 exten-sions, the current taboo extension list is aug- mented, otherwise it is replaced. At startup, the taboo extension list contains .rpmorig, .rpmsave, ,v, .swp, .rpmnew, ~, .cfsaved and .rhn-cfg-tmp-*. |
| weekly | Log files are rotated if the current weekday is less then the weekday of the last rotation or if
more then a week has passed since the last rota-tion. This is normally the same as rotating logs on the first day of the week, but it works better if logrotate is not run every night. |
| yearly | Log files are rotated if the current year is not the same as the last rotation. |
