New LIT command LOGROLL rolls over—rotates— log files. For example: EVENTS.LOG -> EVENTS.L01 -> EVENTS.L02, etc. It's a commonly accepted technique for keeping the current log file from getting endlessly large, while at the same time being able to maintain a number of historical/archived copies.
.LOGROLL wildspec/switches
Switches
|
Switch |
Meaning |
|
Switches affecting user interface: | |
|
/Q |
Query/prompt for confirmation on each file |
|
/F |
Force confirmation—i.e., roll over without asking |
|
Switches limiting selection of files to roll over: | |
|
/MINDAYS:### |
Roll over only files not modified in at least ### days |
|
/MINSIZE:#### |
Roll over only files larger than #### blocks |
|
Switches limiting number of generations of rolled-over files kept: | |
|
/MAXDAYS:### |
Discard rolled-over copies beyond ### days old |
|
/MAXGENS:### |
Discard rolled-over copies beyond ### generations |
Notes
Retention of rolled-over copies stops after MAXDAYS or MAXGENS, whichever comes first. Defaults: DAYS=unlimited, GENS=5. If GENS < 100, rolled-over copies will use extension x##, where x is the first character of the original extension. Else rolled-over copies will use extension ### (001,002,...).