Setup and configuration
Linux
Setup
No additional task are necessary for log rotation on linux.
Configuration
The log rotation on Linux is managed by the linux daemon logrotated
, and is specified in /etc/logrotate.d/supervisor
. See the man pages for logrotated
if you wish to customize the rotation policies.
Rotation Policy
Rotate out the logs weekly, keeping 4 copies.
OS X
Setup
No additional task are necessary for log rotation on OS X.
Rotation Policy
Rotate out the logs when they exceed 100MB in size (the default size in the logrotate.py script).
Configuration
The log rotation on OS X is managed by launchctl/launchd, and the associated .plist files are:
- /Library/LaunchDaemons/com.pipelinefx.logrotate.supervisor.plist
- /Library/LaunchDaemons/com.pipelinefx.logrotate.worker.plist
Both of these plists call /Applications/pfx/qube/utils/logrotate.py;
see The logrotate.py script
Windows
Setup
Configuration
All Scheduled Tasks call %QBDIR%/pfx/qube/utils/logrotate.py,
with only the path to the log as an argument. If you wish to change the
Rotation Policy
Rotate out the logs when they exceed 100MB in size (the default size in the logrotate.py script).
Verifying that log rotation is occurring
- Linux: /var/log/
- OS X: /var/log
- Windows Vista, 7, Server 2008: C:\ProgramData\Pfx\qube\logs
You will see at least on workerlog or supelog file. When rotation occurs, these logs are renamed and/or zipped/compressed.
- supelog -> supelog.1
- supelog.1 --> supelog.2.zip
- supelog.2.zip --> supelog.3.zip
- supelog.3.zip --> supelog.4.zip
- supelog.4.zip is deleted
You will only see supelog and supelog.1 the first time the rotation occurs. The other files will appear when additional log rotation cycles occur as time passes.