Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Traveller''s Lunchbox

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 82 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       logrotate   [-dv]   [-f|--force]  [-s|--state  file]  con­


       logrotate is designed to ease  administration  of  systems
       that generate large numbers of log files.  It allows auto­
       matic rotation, compression, removal, and mailing  of  log
       files.   Each  log  file  may  be  handled  daily, weekly,
       monthly, or when it grows too large.

       Normally, logrotate is run as a daily cron job.   It  will
       not modify a log multiple times in one day unless the cri­
       terium for that log is based on the log's size and  logro­
       tate  is  being run multiple times each day, or unless the
       -f or -force option is used.

       Any number of config files may be  given  on  the  command
       line. Later config files may override the options given in
       earlier files, so the order in which the logrotate  config
       files are listed in is important.  Normally, a single con­
       fig file which includes any other config files  which  are
       needed  should be used.  See below for more information on
       how to use the include directive to accomplish this.  If a
       directory is given on the command line, every file in that
       directory is used as a config file.

       If no command line arguments  are  given,  logrotate  will
       print  version  and  copyright  information,  along with a
       short usage summary.  If any errors occur  while  rotating
       logs, logrotate will exit with non-zero status.


       -d     Turns on debug mode and implies -v.  In debug mode,
              no changes will be made  to  the  logs  or  to  the
              logrotate state file.

       -f, --force
              Tells  logrotate  to force the rotation, even if it
              doesn't think this is necessary.  Sometimes this is
              useful after adding new entries to logrotate, or if
              old log files have been removed by hand, as the new
              files  will  be  created, and logging will continue

       -m, --mail <command>
              Tells logrotate which command to use  when  mailing
              logs.  This command should accept two arguments: 1)
              the subject of the message, and 2)  the  recipient.


       logrotate reads everything about the log files  it  should
       be  handling from the series of configuration files speci­
       fied on the command line.  Each configuration file can set
       global  options  (local  definitions override global ones,
       and later definitions override earlier ones) and specify a
       logfile  to rotate. A simple configuration file looks like

       # sample logrotate configuration file

       /var/log/messages {
           rotate 5
                                     /sbin/killall -HUP syslogd

       "/var/log/httpd/access.log" /var/log/httpd/error.log {
           rotate 5
           mail www@my.org
                                     /sbin/killall -HUP httpd

       /var/log/news/news.crit {
           rotate 2
           olddir /var/log/news/old
                                     kill -HUP `cat /var/run/inn.pid`

       The first few lines set global options;  in  the  example,
       logs  are  compressed  after  they are rotated.  Note that
       comments may appear anywhere in the config file as long as
       the first non-whitespace character on the line is a #.

       The next section of the config files defined how to handle
       the log file /var/log/messages. The log  will  go  through
       five  weekly rotations before being removed. After the log
       file has been rotated (but before the old version  of  the

       The last section defines the parameters  for  all  of  the
       files  in /var/log/news. Each file is rotated on a monthly
       basis.  This is considered a single rotation directive and
       if  errors occur for more then one file, the log files are
       not compressed.

       Please use wildcards with  caution.   If  you  specify  *,
       logrotate  will  rotate  all  files,  including previously
       rotated ones.  A way around this  is  to  use  the  olddir
       directive or a more exact wildcard (such as *.log).

       Here  is  more  information on the directives which may be
       included in a logrotate configuration file:

              Old versions of log files are compressed with  gzip
              by default. See also nocompress.

              Specifies  which  command  to  use  to compress log
              files.  The default is gzip.  See also compress.

              Specifies which command to use  to  uncompress  log
              files.  The default is gunzip.

              Specifies which extension to use on compressed log­
              files, if compression is enabled.  The default fol­
              lows that of the configured compression command.

              Command  line options may be passed to the compres­
              sion program, if one is in use.  The  default,  for
              gzip, is "-9" (maximum compression).

       copy   Make  a  copy of the log file, but don't change the
              original at all.  This  option  can  be  used,  for
              instance,  to  make  a  snapshot of the current log
              file, or when some other utility needs to  truncate
              or  pare  the  file.  When this option is used, the
              create option will have no effect, as the  old  log
              file stays in place.

       create mode owner group
              Immediately  after  rotation (before the postrotate
              script is run) the log file is  created  (with  the
              same  name  as  the  log  file just rotated).  mode
              specifies the mode for the log file in  octal  (the
              same  as  chmod(2)),  owner specifies the user name
              who will own the log file, and group specifies  the
              group  the  log file will belong to. Any of the log
              file attributes may be omitted, in which case those
              attributes  for the new file will use the same val­
              ues as  the  original  log  file  for  the  omitted
              attributes.  This  option can be disabled using the
              nocreate option.

       daily  Log files are rotated every day.

              Archive old versions of log files  adding  a  daily
              extension  like YYYYMMDD instead of simply adding a

              Postpone compression of the previous  log  file  to
              the next rotation cycle.  This has only effect when
              used in combination with compress.  It can be  used
              when some program can not be told to close its log­
              file and thus might continue writing to the  previ­
              ous log file for some time.

       extension ext
              Log  files  are given the final extension ext after
              rotation. If compression is used,  the  compression
              extension (normally .gz) appears after ext.

              Rotate  the log file even if it is empty, overiding
              the notifempty option (ifempty is the default).

       include file_or_directory
              Reads the file given as an argument as  if  it  was
              included   inline   where   the  include  directive
              appears. If a directory is given, most of the files
              in  that  directory  are  read  in alphabetic order
              before processing of the including file  continues.
              The  only  files  which are ignored are files which
              are not regular  files  (such  as  directories  and
              When  using the mail command, mail the just-rotated
              file, instead of the about-to-expire file.

              When using the mail  command,  mail  the  about-to-
              expire file, instead of the just-rotated file (this
              is the default).

       maxage count
              Remove rotated logs older than  <count>  days.  The
              age  is  only  checked  if  the  logfile  is  to be
              rotated. The files are  mailed  to  the  configured
              address if maillast and mail are configured.

              If  the  log file is missing, go on to the next one
              without  issuing  an  error   message.   See   also

              Log  files  are rotated the first time logrotate is
              run in a month (this is normally on the  first  day
              of the month).

              Old  versions  of log files are not compressed with
              gzip. See also compress.

       nocopy Do not copy the original log file and leave  it  in
              place.  (this overrides the copy option).

              Do  not  truncate  the  original  log file in place
              after creating a copy (this overrides the copytrun­
              cate option).

              New  log  files are not created (this overrides the
              create option).

              Do not postpone compression  of  the  previous  log
              file to the next rotation cycle (this overrides the

              Run  prerotate  and  postrotate  scripts  for every
              script which is rotated (this is the  default,  and
              overrides the sharedscripts option).

              Do  not  rotate  the log if it is empty (this over­
              rides the ifempty option).

       olddir directory
              Logs are moved into  directory  for  rotation.  The
              directory  must  be  on the same physical device as
              the log file being rotated.  When  this  option  is
              used  all  old versions of the log end up in direc­
              tory.  This option may be overriden by the noolddir

              The lines between postrotate and endscript (both of
              which must appear on lines by themselves) are  exe­
              cuted  after  the log file is rotated. These direc­
              tives may only appear inside of a log file  defini­
              tion.  See prerotate as well.

              The  lines between prerotate and endscript (both of
              which must appear on lines by themselves) are  exe­
              cuted  before  the  log file is rotated and only if
              the log will actually be rotated. These  directives
              may  only  appear  inside of a log file definition.
              See postrotate as well.

              The lines between firstaction and  endscript  (both
              of  which  must  appear on lines by themselves) are
              executed once before all log files that  match  the
              wildcarded  pattern  are  rotated, before prerotate
              script is run and only if at  least  one  log  will
              actually  be  rotated.  These  directives  may only
              appear inside of a log file definition. See lastac­
              tion as well.


       size size
              Log files are rotated when they  grow  bigger  then
              size  bytes.  If size is followed by M, the size if
              assumed to be in megabytes.  If the k is used,  the
              size  is  in kilobytes. So size 100, size 100k, and
              size 100M are all valid.

              Normally, prescript and postscript scripts are  run
              for  each log which is rotated, meaning that a sin­
              gle script may be run multiple times for  log  file
              entries  which  match  multiple  files (such as the
              /var/log/news/* example). If sharedscript is speci­
              fied,  the scripts are only run once, no matter how
              many logs match the wildcarded  pattern.   However,
              if  none  of the logs in the pattern require rotat­
              ing, the scripts will  not  be  run  at  all.  This
              option overrides the nosharedscripts option.

       start count
              This is the number to use as the base for rotation.
              For example, if you specify 0,  the  logs  will  be
              created  with  a  .0  extension as they are rotated
              from the original log files.  If you specify 9, log
              files  will  be  created  with  a .9, skipping 0-8.
              Files will still be rotated  the  number  of  times
              specified with the count directive.

       tabooext [+] list
              The  current  taboo  extension list is changed (see
              the include directive for information on the  taboo
              extensions).  If  a  +  precedes the list of exten­
              sions, the current taboo  extension  list  is  aug­
              mented,  otherwise  it is replaced. At startup, the
              taboo extension list contains  .rpmorig,  .rpmsave,
              ,v, .swp, .rpmnew, and ~.

       weekly Log  files  are  rotated  if the current weekday is
              less then the weekday of the last  rotation  or  if
              more  then  a  week has passed since the last rota­
              tion. This is normally the same as rotating logs on
              the  first  day of the week, but it works better if
              logrotate is not run every night.





Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can help in many different ways.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds