From owner-freebsd-questions  Fri Aug 25 10:57:06 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA21206
          for questions-outgoing; Fri, 25 Aug 1995 10:57:06 -0700
Received: from misery.sdf.com (misery.sdf.com [204.191.196.34])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id KAA21184
          ; Fri, 25 Aug 1995 10:57:01 -0700
Received: by misery.sdf.com id <1118>; Fri, 25 Aug 1995 10:52:15 +0100
Date: 	Fri, 25 Aug 1995 10:51:55 -0700 (PDT)
From: Tom Samplonius <tom@misery.sdf.com>
To: Nik Malenovic <malenovi@cview.com>
cc: freebsd-questions@FreeBSD.org, freebsd-hackers@FreeBSD.org
Subject: Re: Q: ppp.slattach bugs/ppp server/load balancing
In-Reply-To: <m0sm1O5-0001E4C@tesla.cview.com>
Message-ID: <Pine.BSF.3.91.950825104648.3482B-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: questions-owner@FreeBSD.org
Precedence: bulk


On Fri, 25 Aug 1995, Nik Malenovic wrote:

> 1. has the slattach bug been fixed? under pre-2.0.5-950622-SNAP and the
> mentioned release, slattach has a bug - it doesn't release the comunication
> device when redialing - that would cause your kermit to time out becuase
> it's not able to open the comm device. I fixed it with the simple function
> call - which I am including at the end of the message:

  I just walked someone through setting this up, and it works fine on a 
2.0.5 system.  As I recall, I believe stdin/stdout are connected to the 
port for the re-dial, which is very convienent for "chat".

Tom