From Bugzilla Helper:
Description of problem:
The mgetty (1.1.26-6) doesn't want to start the ppp daemon after the first
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Set up mgetty with Auto-PPP (pap authentication) for dialling in
2.Dial in first (great, it works)
3.Dial in once again (:-((( It doesn't work)
4.Restart the computer and try again.
Only it is in the logs at first:
"mgetty: data dev=ttyS0, pid=28608, caller='none',
conn='28800/V42BIS', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'"
and the next time:
"mgetty: data dev=ttyS0, pid=28676, caller='none',
I'm getting this error:
03/06 23:53:32 yS1 wfr: waiting for ``RING''
03/06 23:53:32 yS1 send: ATA[0d]
03/06 23:53:32 yS1 waiting for ``CONNECT''
03/06 23:53:32 yS1 found action string: ``NO CARRIER''
03/06 23:53:32 ##### failed A_FAIL dev=ttyS1, pid=2013, caller='none', conn='',
Anyone knows if is the same?
I was just working with a customer on a ppp dial-in server issue and it appeared
that mgetty never even attempted to start pppd, on the first connection or
We were trying this with the debug option being passed to pppd and pppd never
started, however we were able to assign the user's shell to a shell script which
called pppd with the same options that mgetty was supposed to send to it. That
worked provided we set SUID root on pppd.
Sorry for the delay in processing this bug - it slipped through the cracks
I can now confirm that the /AutoPPP mode works as documented with all current
Red Hat mgetty releases.