Re: init finagling

From: <bryanm@acsalaska.net>
Date: Fri Sep 08 2006 - 17:58:58 AKDT

On Fri, Sep 08, 2006 at 04:07:31PM -0800, Fielder George Dowding <fgdowding@gmail.com> wrote:
> On 9/8/06, bryanm@acsalaska.net <bryanm@acsalaska.net> wrote:
> >
> >I'm studying the init scripts on my box, and I've found something
> >confusing that I haven't been able to figure out on my own.
> >
> >Consider this list of steps:
> > * I type 'telinit 1' to go to single-user mode
> > * init executes the commands in rc.K, as per /etc/inittab
> > * at the bottom of rc.K is the command 'telinit -t 1 1'
> >
> >This looks like an infinite loop to me. What am I missing?
> >
>
> Oh! Wow! I get to say _RTM_ (notice I am saying it nicely). To wit: the -t 1
> means one second where the second 1 is the run level. From the man page:
> "telinit can tell init how long it should wait between sending processes
> the SIGTERM and SIGKILL signals. The default is 5 seconds, but this can be
> changed with the -t option." So I guess, this is the hurry-up signal.

I did indeed RTM. Notice that the command I use to start the
transition is 'telinit 1'. After I do that, according to inittab,
init processes the commands in rc.K. At the end of that file is
the _same_ command I used to start the transition, signal delay
notwithstanding.

Do you see what I mean? I could just as easily issue the command
'telinit -t 1 1', and the commands would be identical. At what
point does init stop processing commands and give me a prompt?

--
Bryan Medsker
bryanm@acsalaska.net
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Fri Sep 8 17:58:49 2006

This archive was generated by hypermail 2.1.8 : Fri Sep 08 2006 - 17:58:49 AKDT