From owner-freebsd-current Thu Sep 11 00:07:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA03469 for current-outgoing; Thu, 11 Sep 1997 00:07:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA03457 for ; Thu, 11 Sep 1997 00:07:45 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id RAA30497; Thu, 11 Sep 1997 17:05:06 +1000 Date: Thu, 11 Sep 1997 17:05:06 +1000 From: Bruce Evans Message-Id: <199709110705.RAA30497@godzilla.zeta.org.au> To: current@freebsd.org, nnd@itfs.nsk.su Subject: Re: PPP - why set CLOCAL for server ('-direct' mode) ? Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > But then I must ask myself - if this are general >'stdin/stdout' files - what the hell does 'CLOCAL' means >for them ? CLOCAL is meaningless except for ttys. tcsetattr() returns ENOTTY for non-ttys. ppp ignores this error. Modem ioctls are meaningless for some types of ttys. E.g., ioctl(fd, TIOCMGET, &state) returns ENOTTY for ttyv0. ppp handles this a bit better. ppp on ttyv0 can't be expected to work for this and other reasons. In practice, `ppp -direct' on ttyv0 exits after a few seconds before tring any modem ioctls. It prints some gibberish and leaves the tty in a bad state. > 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). ppp should notice the drop and do something appropriate. Perhaps you are using an old version of the cy driver which has broken carrier handling when CLOCAL is set. This is supposed to be fixed in -current, 2.2.0 and 2.1. Bruce