runlevel 4 and rc.M

blian · 04-06-2004, 06:46 PM

*thump*
*thump*
(sound of my head repeatedly hitting the wall)

I have Slackware 9.0 newly installed. When I set the default run level to 3 everything works fine. When I set it to 4 rc.M doesn't run.

My inittab:

Code:

# Default runlevel. (Do not set to 0 or 6)
id:4: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
 
# 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:wait:/etc/rc.d/rc.4

From what I can tell rc.M is never executed for runlevel 4. I removed the my /etc/HOSTNAME file to test and that never got created. Got any ideas?

blian · 04-07-2004, 06:56 PM

OK. I've been doing more reading and I see that rc.M is not run for runlevel 4 (even though inittab says to run it).

Slackware site says that rc.inet1 and rc.inet2 will run in runlevels 2,3, and 4. When I start run level 3 rc.M runs and executes rc.inet1 and rc.inet2. My network gets it's information. When I start run level 4 rc.inet1 and rc.inet2 do not run.

This should happen without me editing rc.4 but I don't see it happening. Should I just run them from rc.4?

subgenius · 04-07-2004, 08:33 PM

The line

rc:2345:wait:/etc/rc.d/rc.M

means that rc.M should execute in runlevels 2, 3, 4, and 5.

In runlevel 4, rc.S should execute first, followed by rc.M then rc.4.

blian · 04-08-2004, 09:30 AM

Quote:

Originally posted by subgenius
The line

rc:2345:wait:/etc/rc.d/rc.M

means that rc.M should execute in runlevels 2, 3, 4, and 5.

In runlevel 4, rc.S should execute first, followed by rc.M then rc.4.

Right. That's what I thought too.

Slackware's website and my PC say otherwise.

When I boot runlevel 4 rc.M never runs. I have to manually run rc.M or rc.inet1 and rc.inet2 to get my network initialized. The ethernet card is showing in ifconfig but the IP address and netmask are not loaded. In runlevel 3 everything works fine.

I tested by commenting out the rc.4 script from inittab. When I reboot (to clear network settings) I don't see the "Going multiuser..." message or the information messages from setting up the network.

Something is wrong but I don't know how to fix it without kludging(sp?) together a script.

scorpiondino · 05-11-2004, 04:45 AM

as far as I know you shouldn't run rc.M & rc.4 together...

I suppose when you go to runlevel 4 it should all work fine.
do you see the dhcpd results (getting ip adress and stuff) during boot?

Quote:

The ethernet card is showing in ifconfig but the IP address and netmask are not loaded. In runlevel 3 everything works fine.

well, try to run "dhcpd eth0" (or eth1, depends on your HW config) after yopu booted to runlevel 4...

hope this helps somehow, and if it doesn't, probably it's some miss-configuration on rc.inet1.conf that is solved in rc.M (cause it has some special initializations...)

datadriven · 05-11-2004, 01:27 PM

Is rc.M chmod 755? It needs to be.