Software: Apache/2.2.3 (CentOS). PHP/5.1.6 

uname -a: Linux mx-ll-110-164-51-230.static.3bb.co.th 2.6.18-194.el5PAE #1 SMP Fri Apr 2 15:37:44
EDT 2010 i686 

uid=48(apache) gid=48(apache) groups=48(apache) 

Safe-mode: OFF (not secure)

/usr/libexec/webmin/logrotate/help/   drwxr-xr-x
Free 50.88 GB of 127.8 GB (39.81%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     intro.html (1.77 KB)      -rw-r--r--

Typically, a log file will be rotated once every day, week or month. The file is usually moved to a new filename and compressed, and a new empty file created in its place. Several generations of these old log files can be kept, so that you can search or generate reports from them even after rotation. Once the number of old logs exceeds a configured limit, the oldest will be deleted.

Each log file being rotated is listed on the module's main page. Each log has its own set of options to control how often it is rotated, how many old copies are kept and so on. You can edit the options for a log by clicking on its filename, or add a new log file using the link at the bottom or top of the table.

Many Linux distribtions include logrotate as standard, and come with configurations for rotating the logs of included servers like Apache and Squid. So even if you have never used this module before, many log files may already be listed on the main page. Often Near the bottom of the page is a button for editing the global configuration, which applies to all log files unless overridden. Below it is a button for setting the schedule on which logrotate is run by Cron, which is necessary for it to actually rotate logs. On most operating systems that include the program as standard, a Cron job will have been already created as part of the installation process.