]>
Commit | Line | Data |
---|---|---|
97359700 PG |
1 | --- ./logrotate.8.org 2007-08-07 11:22:31.000000000 +0200 |
2 | +++ ./logrotate.8 2007-12-24 13:19:07.000000000 +0100 | |
3 | @@ -19,7 +19,7 @@ | |
95d46300 | 4 | in which the \fBlogrotate\fR config files are listed in is important. |
5 | Normally, a single config file which includes any other config files | |
6 | which are needed should be used. See below for more information on how | |
7 | -to use the \fIinclude\fR directive to accomplish this. If a directory | |
8 | +to use the \fBinclude\fR directive to accomplish this. If a directory | |
9 | is given on the command line, every file in that directory is used as | |
10 | a config file. | |
11 | .P | |
97359700 | 12 | @@ -39,14 +39,14 @@ |
95d46300 | 13 | be made to the logs or to the \fBlogrotate\fR state file. |
14 | ||
15 | .TP | |
16 | -\fB-f, -\-force\fR | |
17 | +\fB-f\fR,\fB -\-force\fR | |
18 | Tells \fBlogrotate\fR to force the rotation, even if it doesn't think | |
19 | this is necessary. Sometimes this is useful after adding new entries to | |
20 | \fBlogrotate\fR, or if old log files have been removed by hand, as the | |
21 | new files will be created, and logging will continue correctly. | |
22 | ||
23 | .TP | |
24 | -\fB-m, -\-mail <command>\fR | |
25 | +\fB-m\fR,\fB -\-mail <command>\fR | |
26 | Tells \fBlogrotate\fR which command to use when mailing logs. This | |
27 | command should accept two arguments: 1) the subject of the message, and | |
28 | 2) the recipient. The command must then read a message on standard input | |
97359700 | 29 | @@ -54,10 +54,10 @@ |
95d46300 | 30 | -s\fR. |
31 | ||
32 | .TP | |
33 | -\fB-s, -\-state <statefile>\fR | |
34 | +\fB-s\fR,\fB -\-state <statefile>\fR | |
35 | Tells \fBlogrotate\fR to use an alternate state file. This is useful | |
36 | if logrotate is being run as a different user for various sets of | |
97359700 | 37 | -log files. The default state file is \fI/var/lib/logrotate.status\fR. |
0d3c5cb0 | 38 | +log files. The default state file is \fI/var/lib/misc/logrotate.status\fR. |
91fff036 | 39 | |
40 | .TP | |
41 | \fB-\-usage\fR | |
97359700 | 42 | @@ -392,8 +392,8 @@ |
95d46300 | 43 | \fBsize \fIsize\fR |
44 | Log files are rotated when they grow bigger then \fIsize\fR bytes. If | |
45 | \fIsize\fR is followed by \fIM\fR, the size if assumed to be in megabytes. | |
46 | -If the \fIk\fR is used, the size is in kilobytes. So \fBsize 100\fR, | |
47 | -\fIsize 100k\fR, and \fIsize 100M\fR are all valid. | |
48 | +If the \fIk\fR is used, the size is in kilobytes. So \fBsize \fI100\fR, | |
49 | +\fBsize \fI100k\fR, and \fBsize \fI100M\fR are all valid. | |
50 | ||
51 | .TP | |
52 | \fBsharedscripts\fR | |
97359700 | 53 | @@ -439,7 +439,7 @@ |
95d46300 | 54 | Log files are rotated if the current weekday is less then the weekday |
55 | of the last rotation or if more then a week has passed since the last | |
56 | rotation. This is normally the same as rotating logs on the first day | |
57 | -of the week, but it works better if \fIlogrotate\fR is not run every | |
58 | +of the week, but it works better if \fBlogrotate\fR is not run every | |
59 | night. | |
60 | ||
dd9974c4 | 61 | .TP |
97359700 | 62 | @@ -449,7 +449,7 @@ |
95d46300 | 63 | .SH FILES |
c2c5fb79 | 64 | .PD 0 |
65 | .TP 27 | |
dd9974c4 | 66 | -\fI/var/lib/logrotate.status\fR |
c2c5fb79 | 67 | +\fI/var/lib/misc/logrotate.status\fR |
68 | Default state file. | |
69 | .TP 27 | |
70 | \fI/etc/logrotate.conf\fR |