From owner-freebsd-hackers  Mon Jun  2 14:19:45 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA13059
          for hackers-outgoing; Mon, 2 Jun 1997 14:19:45 -0700 (PDT)
Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13052;
          Mon, 2 Jun 1997 14:19:43 -0700 (PDT)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id RAA27720; Mon, 2 Jun 1997 17:13:27 -0400 (EDT)
Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1])
	by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id RAA00332;
	Mon, 2 Jun 1997 17:19:11 -0400 (EDT)
Message-Id: <199706022119.RAA00332@bmcgover-pc.cisco.com>
To: hackers@freebsd.org, questions@freebsd.org
Subject: re: Need help with pppd...
Date: Mon, 02 Jun 1997 17:19:11 -0400
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Ok. I shot the mouth off too soon. Restructuring all of the parenthesis so
they lined up cleared up a couple of issues. People who use that type of 
indentation and bracket-matching obviously don't do hand traces all that
often :\ (Thats a joke, so please, no flames).

Anyhow, I've reduced myself to one question. Or, more acurately, one point
that I need clarification on. I see now that PPPD leaves the port in a 
non-blocked state for the duration of the call. I guess I don't see why... 
After all, it could be left blocking, and I/O could be first checked for with
a select call. 

I guess the question I really have is this... With the other serial drivers,
what keeps pppd from spinning completely out of control (if its not selecting/
blocking on the async port)?

	-Brian