Eugene Sevinian wrote: > > Thanks Jens, > here is some additional info. > > On Thu, 15 May 1997, Jens B. Jorgensen wrote: > > > Eugene Sevinian wrote: > > > > > > I have installed mgetty ( 1.0.0-1 ) and it works fine when I am dial-in > > > from outside w95 machine. Now I tring to add PPP and here are > > > the basic steps which were done: > > > > > > 1. Installing new kernel (2.0.27) with CONFIG_PPP=m > > > > You didn't use 'make config' or 'make xconfig'? When you recompiled > > the kernel did you make modules and modules-install? You know, the > > PPP module depends on others (can't think of them offhand). > > > > I did it. > > > > 2. Then I edited Makefile in this way > > > CFLAGS=-O2 -Wall -pipe -DAUTO_PPP > > > and slightly modified the policy.h > > > > Did you need to compile from source? The stock binary includes > > AUTO_PPP support. > > > > First I had problems with this binary. Trying to connect from w95 > I got ... > "The computer you're dialing in to cannot establish a Dial_Up > Networking connection. Check your password, and try again." > ... so I decided to compile from source. > > > > 3. Make; cp mgetty /sbin; rebot > > > > > > After this point I get the message > > > "...S1, too fast respawning mgetty. Suspended for 5 min" or something > > > like that. And that is all )-; > > > > If mgetty is respawning, something larger than ppp is probably wrong-- > > it would never have a chance to take a login? Perhaps something you > > did to the config is causing this. Did you change the config file? > > Did you look in /var/log/mgetty/* for error messages? > > Here is the messages coresponding to the new compiled binary "lifetime" > from /var/log/mgetty/mg_ttyS1.log. > -- > 05/15 14:16:54 yS1 mgetty: official release 1.0.0 > 05/15 14:16:54 yS1 check for lockfiles > 05/15 14:16:54 yS1 locking the line > 05/15 14:16:54 yS1 lowering DTR to reset Modem > 05/15 14:16:55 yS1 send: \dATQ0V1H0[0d] > 05/15 14:16:56 yS1 waiting for ``OK'' ** found ** > 05/15 14:16:56 yS1 send: AT[0d] > 05/15 14:16:56 yS1 waiting for ``OK'' ** found ** > 05/15 14:16:56 yS1 waiting... > 05/15 14:45:01 ##### failed dev=ttyS1, pid=10653, got signal 15, exiting >
Signal 15 is SIGTERM--I wouldn't expect this signal to be issued unless you typed 'kill XXX' or some other process intentionally killed the mgetty. Could you perhaps try the stock mgetty? I don't know why SIGTERM would be sent to the mgetty process. Do you have a valid AUTO_PPP entry in /etc/mgetty/login.config? Did you edit this file? (Note that this won't solve your problem with your mgetty perishing all the time--just something you'll need to have to get going.) -- Jens B. Jorgensen [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
