Jacob (Mettavihari)
On Fri, 23 Apr 1999, Ray Olszewski wrote:
> 1. The "respawn" message is definitely a big deal. It means the process is
> starting, ending, and restarting repeatedly. This both consumes a lot of CPU
> time and indicates a configuration error in the inittab line. I don't have
> your prior messages to consult (and in any case you've used several
> variations on the line), so I can't suggest what that error might be. But
> you definitely want to fix it.
>
> 2. What it *might* be is hinted at by these lines taken from the log
> fragment you posted:
>
> >Apr 23 07:04:43 dhamma mgetty[381]: init chat failed, exiting...:
> Interrupted system call
> >Apr 23 07:04:43 dhamma mgetty[381]: failed in mg_init_data, dev=modem, pid=381
> >Apr 23 07:05:59 dhamma mgetty[426]: init chat failed, exiting...:
> Interrupted system call
> >Apr 23 07:05:59 dhamma mgetty[426]: failed in mg_init_data, dev=modem, pid=426
> >Apr 23 07:07:15 dhamma mgetty[431]: init chat failed, exiting...:
> Interrupted system call
> >Apr 23 07:07:15 dhamma mgetty[431]: failed in mg_init_data, dev=modem, pid=431
>
> This makes me think that you somehow have mgetty set up to execute pppd
> (which in turn executes chat) each time it starts ... when what you actually
> want to do is have mgetty execute pppd only after it receives an incoming
> call (or do you even want it to do that? I forget now the details of your
> planned setup).
I finally managed to get rid of the message by using the below lines
----------------
/etc/inittab
s1:345:respawn:/sbin/mgetty /dev/modem /etc/ppp/conf.mgetty.ttyS1 vt100
/etc/ppp/conf.mgetty.ttyS1
# sample uugetty configuration file for a Hayes compatible modem to allow
# incoming modem connections
# alternate lock file to check... if this lock file exists, then uugetty is
# restarted so that the modem is re-initialized
ALTLOCK=cua1
ALTLINE=cua1
# line to initialize
INITLINE=cua1
# timeout to disconnect if idle...
TIMEOUT=60
# modem initialization string...
# format: <expect> <send> ... (chat sequence)
#INIT="" AT\r OK\r\n
WAITFOR=RING
CONNECT="" ATA\r CONNECT\s\A
# this line sets the time to delay before sending the login banner
DELAY=1
#DEBUG=010
---------------------
What I did was to hatch the line
INIT=""AT\r OK\r\n
I presume that this is the line for the chat sequence you mentioned.
I do not fully understand the commands in this file and shall do some
reading on this later.
with thanks
Jacob (Mettavihari)
