Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!EU.net!news.eunet.fi!KremlSun!kiae!relcom!newsserv
From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su>
Newsgroups: comp.os.386bsd.bugs
Subject: Re: sio CLOCAL bug, FreeBSD 1.1 Beta
Date: Fri, 29 Apr 94 01:06:32 +0400
Distribution: world
Organization: Olam HaYetzirah
Message-ID: <LkOL2mj0E0@astral.msk.su>
Sender: news-service@kiae.su
Reply-To: ache@astral.msk.su
Keywords: sio FreeBSD 1.1 Beta COM_BIDIR CLOCAL
References: <199404280058.CAA11555@fasterix.frmug.fr.net>
Summary: writes on the callout device hang if CLOCAL not set
X-Return-Path: kiae!astral!astral.msk.su!ache
Lines: 20
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 911
In comp.os.386bsd.bugs article
<199404280058.CAA11555@fasterix.frmug.fr.net> Pierre Beyssac writes:
>So here it is. When using the callout device, the open() succeeds
>but if CLOCAL is not set, the first write() on the device blocks,
>probably waiting for carrier. If CLOCAL is set (after the open),
>the write does not block.
It isn't a bug, but driver *intended* to do that, !CLOCAL means
that you doesn't access modem anyhow and waiting for carrier, i.e.
CLOCAL --> you can control modem
!CLOCAL --> you *can't* control modem anymore
CLOCAL on outgoing part of bidir device sets automatically after
open.
--
Andrew A. Chernov : And I rest so composedly, /Now, in my bed,
ache@astral.msk.su : That any beholder /Might fancy me dead -
FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead.
RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849