slackware: rc.4 never seems to get executed

Sat Mar 17 01:03:30 UTC 2007

I have been having a few configuration issues with Slack 11. For one, I
am not sure how init gets to runlevel 4. If it does, it never reads
/etc/rc.d/rc.4 or executes it. As a result, the display manager doesn't
run. I can run rc.4 by hand, issuing
    # ./rc.4 start
and kdm starts successfully.

I found this out by running stat on the entire /etc/rc.d directory just
after a reboot. rc.4 had a much older file access time than the rest of the
files, in addition to other files. All the other runlevel files had more
recent access times.

While I don't do much work on /etc/inittab it at least *seems* normal, and
specifies that rc.4 should run during runlevel 4. Here is the listing:

=========LISTING of /etc/inittab FOLLOWS: =====================
#
# inittab       This file describes how the INIT process should set up
#               the system in a certain run-level.
#
# Version:      @(#)inittab             2.04    17/05/93        MvS
#                                       2.10    02/10/95        PV
#                                       3.00    02/06/1999      PV
#                                       4.00    04/10/2002      PV
#
# Author:       Miquel van Smoorenburg, <miquels-X9VMN28TK39om677gZDK1wFcV7zePqp5 at public.gmane.org>
# Modified by:  Patrick J. Volkerding, <volkerdi-qaNcByWzZlFl57MIdRCFDg at public.gmane.org>
#

# These are the default runlevels in Slackware:
#   0 = halt
#   1 = single user mode
#   2 = unused (but configured the same as runlevel 3)
#   3 = multiuser mode (default Slackware runlevel)
#   4 = X11 with KDM/GDM/XDM (session managers)
#   5 = unused (but configured the same as runlevel 3)
#   6 = reboot

# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault:

# System initialization (runs when system boots).
si:S:sysinit:/etc/rc.d/rc.S

# Script to run when going single user (runlevel 1).
su:1S:wait:/etc/rc.d/rc.K

# Script to run when going multi user.
rc:2345:wait:/etc/rc.d/rc.M

# What to do at the "Three Finger Salute".
ca::ctrlaltdel:/sbin/shutdown -t5 -r now

# Runlevel 0 halts the system.
l0:0:wait:/etc/rc.d/rc.0

# Runlevel 6 reboots the system.
l6:6:wait:/etc/rc.d/rc.6

# What to do when power fails.
pf::powerfail:/sbin/genpowerfail start

# If power is back, cancel the running shutdown.
pg::powerokwait:/sbin/genpowerfail stop

# These are the standard console login getties in multiuser mode:
c1:1235:respawn:/sbin/agetty 38400 tty1 linux
c2:1235:respawn:/sbin/agetty 38400 tty2 linux
c3:1235:respawn:/sbin/agetty 38400 tty3 linux
c4:1235:respawn:/sbin/agetty 38400 tty4 linux
c5:1235:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux

# Local serial lines:
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100

# Dialup lines:
#d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100
#d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100

# Runlevel 4 used to be for an X window only system, until we discovered
# that it throws init into a loop that keeps your load avg at least 1 all
# the time. Thus, there is now one getty opened on tty6. Hopefully no one
# will notice. ;^)
# It might not be bad to have one text console anyway, in case something
# happens to X.
x1:4:respawn:/etc/rc.d/rc.4

# End of /etc/inittab
========== END OF LISTING ===============================

The commenting is as-is, un-edited. I don't know why rc.4 is the last line
in this script. Also, should runlevel 4 be included in c1 to c5? I
suspect not, since they are supposed to be TTY consoles.

Any reading suggestions would also be of help. Preferably Slackware-based,
since as you can see in the script comments, this is the *slackware*
method of rebooting.

Under /etc/rc.d, rc.0 is symbolically linked to rc.6.

Thanks

Paul King

--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists