From owner-freebsd-current Wed Sep 10 22:43:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA28715 for current-outgoing; Wed, 10 Sep 1997 22:43:52 -0700 (PDT) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA28707 for ; Wed, 10 Sep 1997 22:43:48 -0700 (PDT) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.7/8.8.7) id JAA25878; Thu, 11 Sep 1997 09:43:34 +0400 (MSD) Date: Thu, 11 Sep 1997 09:43:32 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= X-Sender: ache@lsd.relcom.eu.net To: nnd@itfs.nsk.su cc: current@FreeBSD.ORG Subject: Re: PPP - why set CLOCAL for server ('-direct' mode) ? In-Reply-To: <5v7s4q$4ne@news.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 11 Sep 1997 nnd@itfs.nsk.su wrote: > So the problem (with me) is in (my) interpretation > of '-direct' mode - I suppose (as mentioned - but not defined - in > ppp manual) that in this case 'ppp' works with 'stdin' and 'stdout' > and it is not ppp's task to talk with 'modem' (there can be no > modem at all on the 'stdin/stdout' ?). Yes. > But then I must ask myself - if this are general > 'stdin/stdout' files - what the hell does 'CLOCAL' means > for them ? CLOCAL returns immediately after open. It is for any class of devices which require connection established. If connection established immediately CLOCAL makes no difference at all. The same words about CLOCAL and hangup operation. > Now I use a compromise - I've patched my 'ppp' and > after that it's behavior is more suitable for my purposes > (at least ppp process on my - server - side of a link > sees the CD drop and exits). Correct fix will be to find why modem code is called and remove this call for -direct case. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/