From: NU013809@NDSUVM1.BITNET (Greg Wettstein) Subject: Re: SYS/V init refuses to run my /etc/rc Date: 28 Jan 1993 13:24:08 GMT
I just spent about a week getting the run-level init problem solved on
our network. Previously we had been using the simpleinit but it was
time to move onward. Perhaps I can save people some frustration.
I started with the bootsys3 package but moved over to Michael's sysvinit
after about 24 hours of work. Mike Jagdis is to be complimented on
putting together a nice package but the actual init code needs some
attention.
The first problem is that init will not properly read its inittab file.
This is difficult to notice because the fairly complex system of
initialization files and such seems to mask this basic dysfunctionality.
It took me awhile to figure out what was going on because there is a bug
in the processing of the telinit command options which prevents the user
from ordering a re-read of the inittab file (telinit q). The actual
bug in the parsing of the inittab file is only about a one or two line
patch.
The proper parenting and establishment of session ID's is another story.
This is compounded by the fact that the syslog code in the 4.2 libraries
does not properly set the NOCTTY flag. Mike J has fixed this in his
port of the syslogd daemon but the problem still exists in the libraries.
The long and short of this is that you will sometimes end up with getty's
hooked up to the console (/dev/console) and sometimes without any
controlling tty's whatsoever. I actually stumbled onto this when I
modified the networking daemons so not