From owner-freebsd-hackers  Tue Aug  8 21:03:17 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id VAA12045
          for hackers-outgoing; Tue, 8 Aug 1995 21:03:17 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id VAA12017
          for <freebsd-hackers@freebsd.org>; Tue, 8 Aug 1995 21:03:07 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA03763; Wed, 9 Aug 1995 14:00:39 +1000
Date: Wed, 9 Aug 1995 14:00:39 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199508090400.OAA03763@godzilla.zeta.org.au>
To: cshenton@apollo.hq.nasa.gov, jc@irbs.com
Subject: Re: client & server ppp
Cc: freebsd-hackers@freebsd.org
Sender: hackers-owner@freebsd.org
Precedence: bulk

>I've been dialing into a FreeBSD (Release, -current, and now -stable)
>system running pppd, mostly in server mode, but also dialing back to
>my home (Sunos pppd) in client mode. In both, FreeBSD pppd refuses to
>die and and free up the port for getty (on cuaa0) so I can dial in

It probably needs the `modem' option.

>again from home. FBSD pppd also consumes all CPU available: on a
>system with two pppds, they both run at 50%. W.R.T. die-on-hangup and

I've never seen an overhead problem in pppd.

>Last week I brought up iijppp and with some work, got it running as
>both client and server. It kills ppp when the modem hangs up like it
>should, and uses a modest amount of CPU. Hurray!

In 2.0.5, iijppp consumes all the CPU available while it is transmitting.

Bruce