Provided by: initscripts_2.86.ds1-6ubuntu32_i386 bug


       rcS -- defaults used at boot time


       /etc/default/rcS contains information in the following format:


       Only  one  value per line is allowed. Comments are allowed too and must
       start with the ‘‘#’’ character.


       The following options can be set, the defaults values are shown:

              On bootup the  files  in  /tmp  will  be  cleaned  up  if  their
              modification  time  was  more  than TMPTIME days ago. A value of
              zero means that all files are removed regardless of age. If  you
              don’t  want  the  system to clean /tmp set TMPTIME to a negative
              value (-1) or the word infinite.

              Setting this to yes causes  init  to  spawn  a  sulogin  on  the
              console  as  one of the first things in the boot process. If the
              administrator does not login, the sulogin will timeout after  30
              seconds and the boot process will continue.

              Normally  the  system  will  not let anyone login until the boot
              process is complete and and the system has come up completely in
              the  default  runlevel  (usually level 2). However theoretically
              it’s possible to login a bit earlier, as soon as /usr/sbin/inetd
              is started. The default value of no prevents this, setting it to
              yes allows it.

       UTC=   This is used to interpret  the  system  (BIOS)  clock.  If  this
              option  is  set  to no the system clock is supposed to be set at
              local time. If this option is set to yes  the  system  clock  is
              supposed to be set at UTC (Universal Time, a.k.a. GMT).

              Setting  this  option  to  no  will  make  the bootup a bit less

              At boot time the  system  edits  the  first  line  of  the  file
              /etc/motd and replaces it with the output from the command uname
              -a. Setting this to no prohibits that.

              When the root  and  all  other  filesystems  are  checked,  this
              happens  with  the  -a flag which means autorepair. If there are
              really big inconsistencies, the fsck will bail out.  The  system
              will  print  a  message  asking  the administrator to repair the
              filesystem maually and 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 always repair the filesystems without
              any  interaction  but  might  irreversibly  damage   your   file


       Miquel van Smoorenburg <>


       init(8), inittab(5).

                                  03 Nov 2003                           rcS(5)