mgetty spawning too fast?

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi all.

I'm running RedHat 2.0 Linux (1.2.13-ELF) and am having several
frustrating problems with mgetty.  I have a ZOOM 28.8 internal
V.FAST (pre v.34) modem.  Before, running non-ELF slakware, I
had NO problems with mgetty.

First, when I build and install 0.98 (which all goes fine), and then
enter it into inittab with a line such as:

d1:2345:respawn:/usr/sbin/mgetty ttyS1

and reboot, I start getting an error message stating:

d1 respawning too quickly, disabling for 5 minutes ...

and then mgetty is disabled.  Five minutes later, I get the same
error message, and again it's hosed.  It never successfully
runs.  Kaputt.

Any ideas why this might be?  I never had this problem on non-ELF slakware.

Second, I can successfully install the RedHat RPM of mgetty (0.22), and
it runs ok at first, meaning that it loads and I don't get the
respawning too quickly error message.  I am then able to connect,
log in, and run pppd, and do whatever I want.  But when I disconnect,
mgetty disappears (actually, it seems to disappear as soon as the connection
is made, at least it disappears out of ps ax display), and is NEVER respawned.
Thus, I get one call in and the game is over.  Mgetty is dead and the
modem will never answer again.

Why might this be?  Any ideas?  As you can see, on my system, mgetty
will either respawn too quickly or not respawn at all.

Third, is there any way, at runtime, to tell mgetty where the 
mgetty.config file is located?  Or, failing that, to look at the
mgetty file itself and determine the (compiled-in) location of the 
mgetty.config file?  The RedHat RPM doesn't provide a default mgetty.config,
and since the source code is not provided with the RPM, I don't
know what the compiled-in defautls were.  So I have no clue as to
where to put my mgetty.config file.

Any help on any of this would be greatly appreciated.  Thank you
in advance for any assistance.  As you can see, I'm being stopped
on every front!

Mark

**************************************************************
Mark Shacklette					mshack@mcs.com
Lake Shore MicroTech Group, Inc.				
**************************************************************