From owner-freebsd-hackers Wed Aug 9 08:54:52 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id IAA19059 for hackers-outgoing; Wed, 9 Aug 1995 08:54:52 -0700 Received: from thing.sunquest.com (thing.Sunquest.COM [149.138.1.11]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id IAA19044 for ; Wed, 9 Aug 1995 08:54:47 -0700 From: tony@thing.sunquest.com Received: by thing.sunquest.com; id AA02529; Wed, 9 Aug 1995 08:50:34 -0700 Message-Id: <9508091550.AA02529@thing.sunquest.com> To: Bruce Evans Cc: hackers@freefall.freebsd.org X-Mailer: Rand MH v6.7 Transport-Options: /nodelivery/return Subject: Re: client & server ppp In-Reply-To: Your message of "Wed, 09 Aug 95 13:11:30 +1000." <199508090311.NAA02181@godzilla.zeta.org.au> Date: Wed, 09 Aug 95 08:50:34 -0700 X-Mts: smtp Sender: hackers-owner@FreeBSD.org Precedence: bulk > Perhaps kermit is being misused. If you terminate it without hanging up > and before starting pppd, and then try to start pppd, then there will be > a race between pppd and getty to grab the port. getty will probably win. > If you terminate kermit normally then it will hang up. Then there should > be no races, but kermit will be of no use for starting pppd sessions. > > These problems may be avoided in many different ways: > 1. suspend kermit instead of exiting from it. > 2. some kludge to hold the device open after exiting from kermit. > 3. run kermit from inside pppd. > 4. run something simpler than kermit from inside pppd. I agree with all of the above. I got some excellent help from John Capo , and will be looking at using pppd's built in chat option. My only remaining comment regarding use of kermit is that maybe it should be removed from the FAQ (/usr/share/FAQ/Test/ppp....). I basically followed the instruction contained for setting up client side PPP including the use of kermit scripts (which I pretty much copied verbatim) I'd be happy to make some alterations to the PPP FAQ if folks think it is worthwhile. tony