Re: SysVinit (again)

Jeff Coy Jr. (jcoy@jcoy-ppp.cscwc.pima.edu)
Sat, 27 Apr 1996 01:45:15 -0700 (MST)


On Thu, 25 Apr 1996, Steven N. Hirsch wrote:

> > So, all my old scripts are executed. So far so good. The real trouble is that AFTER these
> > scripts are done, there comes ..silence.. for about 10 seconds. Next thing I see is 6 lines
> > of error messages saying "INIT": "1": respawning too fast; disabled for 5 min. This is then
> > repeated with "2", "3", "4" and "5". Then nothing...
> >
>
> > # Format:
> > # <id>:<runlevels>:<action>:<process>
> > 1:2345:respawn:/sbin/getty 9600 tty1
> > 2:23:respawn:/sbin/getty 9600 tty2
> > 3:23:respawn:/sbin/getty 9600 tty3
> > 4:23:respawn:/sbin/getty 9600 tty4
>
>
> ## 5:23:respawn:/sbin/getty 9600 tty5
> ## 6:23:respawn:/sbin/getty 9600 tty6
>
> I've seen the same thing with my ancient version of sys V init. Just comment out the
> last two lines. For some reason, my system does not want to cooperate with more than
> (4) consoles.
>
or use agetty instead:

1:2345:respawn:/sbin/agetty 38400 tty1 linux
2:23:respawn:/sbin/agetty 38400 tty2 linux
3:2:respawn:/sbin/agetty 38400 tty3 linux
4:2:respawn:/sbin/agetty 38400 tty4 linux
5:2:respawn:/sbin/agetty 38400 tty5 linux
6:2:respawn:/sbin/agetty 38400 tty6 linux

working fine for me.

jeff

---
Why Linux? source code. POSIX. tcpip. job control. support from the authors.
drivers for most hardware.  because one terminal or process is never enough.
    forget the other O/Ss, i use Linux- the choice of a GNU generation.