Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error: init: Id "s1" respawning too fast: disabled for 5 minutes

1,589 views
Skip to first unread message

Andrew Cook

unread,
Nov 14, 1997, 3:00:00 AM11/14/97
to

Hi

Since I upgraded my system from slackware 3.1 to 3.4, I am
continuoualy getting the following error message posted to my console:

INIT: Nov 10 05:39:29 anchty init: Id "s1" respawning too fast: disabled for 5 minutes
Id "s1" respawning too fast: disabled for 5 minutes
INIT: Nov 10 05:44:51 anchty init: Id "s1" respawning too fast: disabled for 5 minutes
Id "s1" respawning too fast: disabled for 5 minutes

When it happens, it screws up my modem/ppp link. What usually causes this?
The init man page suggests that it is a syntax error in /etc/inittab. My
inittab entry for s1 is as follows:

# Modem dialin/dailout line
s1:12345:respawn:/sbin/uugetty ttyS1 F38400 vt100

This is the same syntax I used in my old setup, which was not plagued by
this problem. As far as I can tell, this should be OK. This is the only
reference to s1 or ttyS1 in my inittab.

Does anyone know whats gives?

Thanks,

-Andy Cook
an...@anchtk.chm.anl.gov

kent

unread,
Nov 17, 1997, 3:00:00 AM11/17/97
to


Andrew Cook <an...@anchtk.chm.anl.gov> skrev i artiklen
<64hq7t$5...@senator-bedfellow.MIT.EDU>...

Try

/sbin/uugetty ttyS1 F38400 vt100

from a root shell. The errormessage you'll get should tell you something
about
what to fix.

Kent

--
Linux 1.0 is out: NT 5.0 is now obsolete


Richard Marko

unread,
Nov 19, 1997, 3:00:00 AM11/19/97
to

> > INIT: Nov 10 05:39:29 anchty init: Id "s1" respawning too fast: disabled for 5 minutes

ttySx respawning too quickly information for others that still be having
this problem.

I tried various settings for ttyS2 in inittab. Changed setserial in
rc.local and still had the problem that when my wife logged off I would
get the message "S2 respawning too fast. Disabling for 5 minutes".

After 2 weeks and lots of helpful messages from everyone (Thanks guys!)
I finally located the problem and everything is working great now.

Evidently mgetty (I didn't realize until I was reading the man page and
mgetty.info.gz for the umpteenth time) looks at gettydefs for
respawning. Once I added the lines reflecting the 57600 baud rate,
everything works flawlessly.

The null modem connection was set at 57600 baud but gettydefs only had
lines for up to 38400 baud. I had to add lines throughout gettydefs that
reflected this baud baud rate.

Evidently mgetty (I didn't realize until I was reading the man page for
the umpteenth time) looks at gettydefs for respawning. Once I added the
lines reflecting the 57600 baud rate, everything worked flawlessly.

Now I am no longer in the dog house with the wife. Chuckle. Actually, I
wasn't in the dog house but she was beginning to wonder if I would ever
get the problem fixed or not.

0 new messages