Rotation schedule
  Controls how often the log is rotated.

Maximum size before rotating
  Sets a limit on the size of the log file before it is rotated. This field can be used instead of the rotation schedule if you prefer a size rather than time-based limit.

Number of old logs to keep
  Determines how many old generations of the log file to save. These will typically have the same name as the original log, but with .0, .1 and so on appended. If your enter 0, no old logs will be kept and thus the contents of the log file will be lost when it is rotated.

Compress old log files?
  When this option is enabled, old logs will be compressed with `gzip` after rotation to reduce the amount of disk space that they consume.

Rotate even if log file is empty?
  If enabled, this option tells `logrotate` to still rotate the log file even if it is empty, resulting in old copies with zero size being saved.

Re-create log file after rotation?
  When this option is enabled, the log file will be re-created after rotation instead of simply being left for the server that writes to it to re-create. By default it will be created with the original permissions and owner, but you can use the fields next to the Yes option to specify alternate file permissions, user and group.

Store old rotated logs in
  When this field is set to Same directory as log file, the old rotated copies of the log file will be stored in the same directory as the original log. The Directory option can be used to specify an alternate location - however, it must be on the same filesystem as the log file.

Commands to run after rotation
  When this text box is filled in, the entered shell commands will be run after the log has been rotated. Many servers need to be re-started after their log has been renamed, so that they will write to the new file properly. In this case, you might enter a command like killall -HUP httpd to trigger a re-start after rotation.