getty respawning too rapidly on serial port attached to modem

getty respawning too rapidly on serial port attached to modem

Post by Vicky Sellar » Wed, 11 Nov 1998 04:00:00



Whichever serial port I attach the modem to (either direct serial
connection or via an 8 port serial adaptor) it produces the error message
"ttyn/usr/sbin/getty /dev/ttyn Command is respawning too rapidly"  (n being
the tty number the modem is attached to) to the console and error log. This
has always happened since installation. The only way I can get a connection
to the modem is by stopping the respawn to all serial ports (init N), using
ate to start a modem session and then re-starting all gettys (init q) and
so getting a login prompt.

Does anyone know a way of stopping this by, maybe, slowing the rate of
respawn if this is possible? or any other fix?

Vicky Sellars
Lynx Heywood Ltd

 
 
 

getty respawning too rapidly on serial port attached to modem

Post by Matt Willma » Wed, 11 Nov 1998 04:00:00


We've seen this before when the modem is configured to "echo"
all of the commands sent to it.  Turn off the local echo on the modem
( can't remember the AT command off the top of my head ), and your
problem should go away.

Matt


> Whichever serial port I attach the modem to (either direct serial
> connection or via an 8 port serial adaptor) it produces the error message
> "ttyn/usr/sbin/getty /dev/ttyn Command is respawning too rapidly"  (n being
> the tty number the modem is attached to) to the console and error log. This
> has always happened since installation. The only way I can get a connection
> to the modem is by stopping the respawn to all serial ports (init N), using
> ate to start a modem session and then re-starting all gettys (init q) and
> so getting a login prompt.

> Does anyone know a way of stopping this by, maybe, slowing the rate of
> respawn if this is possible? or any other fix?

> Vicky Sellars
> Lynx Heywood Ltd


 
 
 

1. internal modem vs. serial port: getty respawns too fast

Howdy...after lots of reading I've managed to get an old Zenith 8086
portable set up as a dumbterm.  The only problem is that the only hardware
config I've had any success with requires disconnecting my trackball
and plugging the terminal into its port (/dev/ttyS0).  Anything else
gives me getty respawning too fast: disabled for 5 minutes.

Here's my current hardware setup wrt serial ports etc...
serial trackball on /dev/mouse -> /dev/ttyS0
internal modem on /dev/modem -> /dev/cua1
Straight-through RS232 cable w/ a null modem adaptor and various gender
changers on it which connects (sometimes) the 8086 to the 586.

I've got two 9-pin male ports on the back of my 586, but it seems like
the modem has control over the second 9-pin port for some reason.  I've
tried changing the IRQ for that 9-pin port to be different from /dev/cua1,
but then getty respawns too fast when i change my getty respawn to ttyS2
or whatever.  Basically, i can't get my dumbterm to work off of anything
besides my mouse port...help! :)

Thanks,
- Eric

--
Eric Sakowski aka Lem aka Ouroboros  
Computer Operator, Systems Dept., RU Libraries Tech Services
http://remus.rutgers.edu/~worm

2. Moving to Solaris 9 - start fresh?

3. SCO UNIX console getty respawning too rapidly - why?

4. Using NTP to Control and Synchronize System Clocks - Part III

5. getty respawning too rapidly

6. which SCSI driver shuld I use?

7. "Getty respawning too rapidly" ... again

8. Where can I find ss spreadsheet?

9. Getty Spawning to rapidly on Dial up modems

10. help with getty, respawn & serial stuff

11. how do you read from serial port attached to modem

12. Serial port to serial port with null modem cable

13. respawning too rapidly