🚀 go-pugleaf

In article <dhatz.744498408@news.forth.gr> dhatz@pythia.csi.forth.gr (Dhmhtrhs Hatzopoulos) writes:
>Hello!
>
>I'd appreciate it very much, if someone who has successfully setup
>SCO's PPP (from SCO TCP/IP v1.2.0i) would give me a few hints about 
>it. I'm trying to configure it to operate over dialup serial links,
>but it won't work any more after handling the first incoming call
>successfully ... So I have to manually kill and restart the pppd daemon
>everytime!

PPP is BROKEN BROKEN BROKEN.  I have pulled out a substantial
qunatity of hair trying to get it to work.  The difficulties are
so numereous, I'll just enumerate them:

1.  Hardware flow control is not there.  High speed
modems are thus out.  I recently was able to work around this by
using ditty, digiboard's port control utility.

2.  pppd does not seem to notice when the line drops.
		
3.  Timeout parameters do not work as advertized.

According to SCO,  these things have been fixed in the ODT 3.0
release.  However, those of us running ODT 2.0 (and tcpip 1.2.0)
are screwed, because SCO has not commited to releasing a fixed
ppp for older releases.  

>From what I can tell (reading /usr/adm/syslog entries), ppp (nppp's
>login shell) receives a sighup once the dialin line disconnects, but
>doesn't properly detach the tty. The next time nppp logs in, 'w' doesn't
>report '-ppp' as nppp's shell and 'ps' reports that 'ppp' doesn't have
>a controlling tty.

I have found that simply killing the stuck pppd often loosens
things up.   When connections are terminated normally, ie via a
shutdown, things seem to work a little better.

<Pleas deleted>

-- 
Robert Sexton - robert@lunatix.lex.ky.us, ukma!lunatix!robert
	Lexington Public Access UNIX -KY- (606) 255-9121
	Anarchy: It's not the Law, It's just a good Idea.