Provided by: initscripts_2.88dsf-13.10ubuntu11_amd64 bug


       rcS - variables that affect the behavior of boot scripts


       The /etc/default/rcS file contains variable settings in POSIX format:


       Only one assignment is allowed per line.  Comments (starting with '#') are also allowed.


       The   following   variables   can   be   set.    For   the   default   values  please  see

              On boot the files in /tmp will be deleted if their modification time is  more  than
              TMPTIME days ago.  A value of 0 means that files are removed regardless of age.  If
              you don't want the system to clean /tmp then set TMPTIME to a negative value (e.g.,
              -1) or to the word infinite.

              Setting this to yes causes init to spawn a sulogin on the console early in the boot
              process.  If the administrator does not login then the sulogin  session  will  time
              out after 30 seconds and the boot process will continue.

              Normally  the  system  will not let non-root users log in until the boot process is
              complete and the system has finished switching to  the  default  runlevel  (usually
              level  2).   However, in theory it is safe to log in a bit earlier, namely, as soon
              as inetd has started.  Setting the variable to no allows earlier login; setting the
              variable to yes prevents it.

              Some   details:   The   DELAYLOGIN  variable  controls  whether  or  not  the  file
              /var/lib/initscripts/nologin is created during the boot process and deleted at  the
              end  of  it.   /etc/nologin is normally a symbolic link to the latter location, and
              the login(1) program refuses to allow non-root logins so long as  (the  target  of)
              /etc/nologin  exists.  If you set the variable to no then it is advisable to ensure
              that /var/lib/initscripts/nologin does not exist.

       UTC    This is used to govern how the hardware real time clock is interpreted when  it  is
              read  (e.g., at boot time, for the purpose of setting the system clock) and when it
              is written (e.g., at shutdown).  If this option is set to no then the system  clock
              is  assumed  to  be set to local time.  If the option is set to yes then the system
              clock is assumed to be set to something approximating  Coordinated  Universal  Time
              (UTC).  (POSIX systems keep a variant of UTC, without leap seconds.)

              On   contemporary   Debian   systems   (although   change  has  been  requested  at
    , if UTC is set to no then  /usr/share/zoneinfo  must
              be  readable  early  in  the  boot process.  If you want to keep /usr on a separate
              filesystem then you must still ensure that the target of /etc/localtime  points  to
              the  correct  zone  information  file  for  the  time zone of the time kept in your
              hardware real time clock.

              Setting this option to no (in lower case) will make the boot  process  a  bit  less
              verbose.  Setting this option to yes will make the boot process a bit more verbose.

              When  the  root and all other file systems are checked, fsck is invoked with the -a
              option which means "autorepair".  If there are major inconsistencies then the  fsck
              process will bail out.  The system will print a message asking the administrator to
              repair the file system manually and will present a root shell  prompt  (actually  a
              sulogin  prompt)  on  the  console.   Setting  this  option  to yes causes the fsck
              commands to be run with the -y option instead of the -a  option.   This  will  tell
              fsck always to repair the file systems without asking for permission.


       The EDITMOTD and RAMRUN variables are no longer used.


       Miquel van Smoorenburg <>


       inetd(8), init(8), inittab(5), login(1).

                                           16 Jan 2006                                     rcS(5)