On Wed, 21 Mar 2007 14:55:42 +0000 (WET)
Jorge Almeida <[EMAIL PROTECTED]> wrote:
> On Wed, 21 Mar 2007, TheOldFellow wrote:
>
> > On Wed, 21 Mar 2007 13:01:06 +0000 (WET)
> > Jorge Almeida <[EMAIL PROTECTED]> wrote:
> >
> >> I'm using runit as alternative to sysvinit. Booting is no problem.
> >> Rebooting is terribly slow. After issuing "init 6", a
> >> normal-looking message appears, concerning services to stop. Then
> >> nothing for a long time. If I press <Ret>, I get the shell prompt,
> >> and I can do "ls", for example. It would seem that it won't
> >> reboot. But it does, eventually. I can't grab the last messages,
> >> which go too fast.
> >
> > If you logout of your last shell does it go faster? There seems to
> > be some delay before a tty is shut down.
> I was doing it from the console, as root. X wasn't running, and there
> wasn't any other shell running. Anyway, the "normal-looking messages"
> said the getty services were down, so the big delay must be elsewhere.
> (OTHH, VC1 had a getty, since the shell prompt still appeared...)
OK, you still have to exit the last shell, otherwise you have to wait
while it times out and kills it.
> >> (I'm not sure whether this is the correct list for this kind of
> >> question...)
> >
> > I'd use gmane.comp.sysutils.supervision.general
> I thought about it, but then stage 1 uses LFS boot scripts...
> >
> BTW: Would you mind posting your networking boot scripts? (Or, better
> said, your networking services scripts?). From what little I
> understand of networking, the boot scripts load the kernel with
> information about networking, and this seems an initializing task,
> not an ongoing service. But you said (some time ago) that you run it
> as a service. I'm curious about it...
The way I do networks as runit services...
1) I wrote a little C program to wait:
/* pause.c */
main ()
{
exit (pause());
}
2) Then a service script like this:
#!/bin/bash
# modprobe eth0 if this is required to load a NIC module
exec 2>&1
# use the regular LFS network script to bring up the connection
/etc/sysconfig/network-devices/ifup eth0
# and wait until we get a TERM or KILL signal
exec pause
3) and a finish script:
#!/bin/bash
# bring the connection down
/etc/sysconfig/network-devices/ifdown eth0
I've often wondered if I could dispense with the pause program, but
everything I tried failed, so I just use that.
HTH,
R.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
