UUGETTY respawning too rapidly?

UUGETTY respawning too rapidly?

Post by PERUCCI, PHILIP » Sat, 06 Nov 1993 20:35:36



I am currently trying to get uugetty (getty_ps) working with
Slackware 1.0.5.

With everything configured, at boot time I get a message about

"c7: respawning too rapidly: disabled for 5 minutes"

(note that the message is not verbatim - it is from memory).  Anyone
know what might cause this?  I know it takes some doing to get this
working...

Can anyone comment on:

  1: The respawning too rapidly message?

  2: Must echo be DISABLED on the modem (Q and E AT commands)?

  3: What about the DTR modem response (&D AT command)?

  4: Is DEBUG=777 in /etc/default/uugetty.ttyS0 all that is required for
     trace?  I have this, but get nothing in /tmp.

  5: In /usr/adm/getty.log, I get nothing but "cannot connect" messages.

I have all the READMEs, the HOWTO, and the NET-book (doc project) -
and I read them.  Read man pages for getty and gettydefs too.

Still I am missing something...

---------------------------------------------------------------------------
 Phil Perucci, Systems Programmer   | "I don't speak for any organization

---------------------------------------------------------------------------

 
 
 

UUGETTY respawning too rapidly?

Post by Andy McFadd » Sun, 07 Nov 1993 06:23:50



Quote:>Can anyone comment on:

>  1: The respawning too rapidly message?

You have an entry in your inittab (or whatever Linux uses) to restart
UUGETTY whenever it dies.  However, it's exiting/crashing/whatever right
after it starts up.  To keep your system from becoming unusable, init
won't try to execute the command again for 5 minutes.

You can usually find out what the problem is by executing the command
directly, and looking at the output.  Around here, we get that message
a lot because ttymon dies whenever the access permissions or major/minor
number on a /dev/ entry are wrong.  (In fact, this very morning... urgh.)

Quote:>  5: In /usr/adm/getty.log, I get nothing but "cannot connect" messages.

Try running it manually; hopefully it'll tell you why.

--

"Our UNIX is bigger than your UNIX"
[ These are my opinions, not Amdahl policies. ]

 
 
 

UUGETTY respawning too rapidly?

Post by Christian Hen » Mon, 08 Nov 1993 13:44:54




Quote:>I am currently trying to get uugetty (getty_ps) working with
>Slackware 1.0.5.

>With everything configured, at boot time I get a message about

>"c7: respawning too rapidly: disabled for 5 minutes"

>(note that the message is not verbatim - it is from memory).  Anyone
>know what might cause this?  I know it takes some doing to get this
>working...

>  2: Must echo be DISABLED on the modem (Q and E AT commands)?

With some systems, it seems to depend upon which device driver you access for
your comm port.  Personally, I have echo on and ALL result codes enabled (in
other words, my personal answer to your question is a definite "NO").

Quote:>  3: What about the DTR modem response (&D AT command)?

I'd suspect that AT&D3 would be the safest.  If your modem is as strange as
mine, you'll have to settle for AT&D2 (When I use &D3, my modem refuses to
use v.42bis after a disconnection until I send an ATZ again (but that's
another story...  :-) )).

Quote:>I have all the READMEs, the HOWTO, and the NET-book (doc project) -
>and I read them.  Read man pages for getty and gettydefs too.

>Still I am missing something...

Try using /dev/cua0 instead of /dev/ttyS0.  It seems to cause less problems for
some people (in fact, I've never been able to use /dev/ttyS? successfully for
over 10 minutes straight (!)).

As an example, here's a copy of my  uugetty.cua0 :

-------------------------------------------------------------------------------
SYSTEM=reality          # naturally, this will be different for you ;->
VERSION=/proc/version
LOGIN=/bin/login
ISSUE=/etc/issue        # unrelated to your problems, but it _is_ in mine :-/
CLEAR=NO                # preferance.  I, personally, don't like the screen
                        #   clearing at the point where this would cause it
                        #   to occur.
HANGUP=YES              # this one's well documented.
INIT="" ATZ\r OK ATV1Q0M0&C1&D2\r OK
ALTLINE=ttyS0           # Just because I don't use /dev/ttyS0 doesn't mean I
ALTLOCK=ttyS0           #   (or someone else) will never accidentally try to
                        #   grab it.  <grin>
INITLINE=cua1
TIMEOUT=60
DELAY=1                 # Longer "Login incorrect" delays just serve to
                        #   royally p*ss me off when I'm having one of my
                        #   bad typing days.  :-)
WAITFOR=RING            # Why depend upon auto-answer when you don't have to?
CONNECT="" ATA\r CONNECT\s\A  # Actually, I could care less about what
                                #   follows the "CONNECT" message, becuase I'm
                                #   using a locked bps rate anyway.
-------------------------------------------------------------------------------

In addition, my /etc/gettydefs and /etc/gettytab are almost exactly the
defaults given in the Slackware 1.0.4 (most likely 1.0.5 too) installation.
The only change I recall making to these files was uncommenting the 38400# line
if it was commented out.

With this configuration, I'm able to use uugetty well along with UUCP 1.04 (?)
and Kermit.

See if this helps you any.  :-)

--
  |  Christian Henry...          |  "If there's a new way,                  |
  |      ...North York, Ontario  |   I'll be the first in line,             |
  |                              |   But it better work this time!"         |

 
 
 

UUGETTY respawning too rapidly?

Post by Rafal Kust » Sat, 13 Nov 1993 14:58:35





>>I am currently trying to get uugetty (getty_ps) working with
>>Slackware 1.0.5.

>>With everything configured, at boot time I get a message about

>>"c7: respawning too rapidly: disabled for 5 minutes"

>>(note that the message is not verbatim - it is from memory).  Anyone
>>know what might cause this?  I know it takes some doing to get this
>>working...

>>  2: Must echo be DISABLED on the modem (Q and E AT commands)?

I had uugetty working, and suddenly, I started having above problem.
It simply means that getty exits almost immediately, supposively with
error code. I just grabbed getty_ps sources again, and recompiled. I
also remmember, when installing, that I would have that problem. Debug
file would show 'Could not open init line' or something. I remmember
that setting (or unsetting) a define on SYSV init would help. Try
that.

                                Rafal

>[good advice deleted]
>See if this helps you any.  :-)
>--
>  |  Christian Henry...          |  "If there's a new way,                  |
>  |      ...North York, Ontario  |   I'll be the first in line,             |
>  |                              |   But it better work this time!"         |


--
/|| Numbers exist only in our minds. There is no physical entity that
 ||_is_ number 1. If there were, 1 would be in a place of honor in
 || some great museum of science, and past it would file a steady
==== stream of mathematicians gazing at 1 in wonder and awe.
 
 
 

UUGETTY respawning too rapidly?

Post by Dan Everha » Tue, 09 Nov 1993 11:15:36





> >I am currently trying to get uugetty (getty_ps) working with
> >Slackware 1.0.5.

> As an example, here's a copy of my  uugetty.cua0 :

Another helpful thing is to add the line

DEBUG=777

to the uugetty.xxx file.  This will create a debugging transscript in
/tmp.

--
  _                              

 \_/ \_________________________________________   206-743-6982, 742-8604 (fax)
 / \_/                                            7107 179th St SW
 \_/   Quality Software and Hardware Consulting   Edmonds, WA 98026, USA

 
 
 

1. respawning too rapidly

hiya,

trying to setup a minimal linux system on a laptop...

Have installed a root filesystem as described in the boot/rescue disk howto.
libraries and executables based on RH 6.2 tools...

It'll boot and mount root, and gets to runlevel 2, and the mingetty's are suspended cause they're respawning too rapidly.. why?
my setup:

(Kernel 2.4.5)

cat inittab
id:2:initdefault:
si::sysinit:/etc/rc
l0:0:wait:/etc/rc0
l2:2:wait:/etc/rc2
l6:6:wait:/etc/rc6
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2

cat rc
#!/bin/sh
/bin/mount -av
/bin/loadkeys /lib/us.kmap

ls -l /dev/tty[12]
crw-r--r--    1 root     root       4,   1 Jun  6 08:14 ../dev/tty1
crw-r--r--    1 root     root       4,   2 Jun  6 08:05 ../dev/tty2

ls -l /sbin/mingetty
-rwxr-xr-x    1 root     root         8112 Feb  3  2000 /sbin/mingetty

2. 16 bits color ??? (with Cirrus 54M30 & Vobis monitor) HOW????

3. GCC 2.7.2.1 include files.

4. /dev/console respawning too rapidly (Install of AIX3.2.1.)

5. Very strange, wireless NIC brings down my network!

6. mingetty respawning too rapidly

7. SBLive Problems

8. INIT: Command respawning too rapidly...

9. HELP Please - "command is respawning too rapidly"

10. "tty respawning too rapidly" on twinax displays (terminals)

11. HELP: INIT - respawning too rapidly????

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