Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!ctisbv!pim
From: pim@cti-software.nl (Pim Zandbergen)
Newsgroups: comp.sources.d
Subject: Re: Bugs in Pcomm 1.2(.8)
Keywords: bugs, logic errors
Message-ID: <1685@ctisbv.cti-software.nl>
Date: 3 Feb 90 12:12:24 GMT
References: <1101@trancb.East.Sun.COM>
Organization: CTI Software BV, The Hague, the Netherlands
Lines: 18

matthew@sunpix.East.Sun.COM ( Sun Visualization Products) writes:

>2) Pcomm does not handle dial-in/dial-out lines correctly.  It assumes that
>   if it can get a LCK file for a device, that it owns the device.  This is
>   partially correct.  An initial open() needs to be accomplished to test if
>   the device is currently being used as an dial-in line.  If 'open()' returns
>   and error code of 'EBUSY', the device is being used as a dial-in line, and
>   should be handles as a LCK'd device. (my patch for GETPORT fixes this)

Rather than relying on device driver dependent error codes,
one could probably better use uugetty on this line.
In that case, there *will* be a LCK file if the line is used
as a dial-in line.
-- 
Pim Zandbergen                           domain : pim@cti-software.nl
CTI Software BV                          uucp   : uunet!mcsun!hp4nl!ctisbv!pim
Laan Copes van Cattenburch 70            phone  : +31 70 3542302
2585 GD The Hague, The Netherlands       fax    : +31 70 3512837