Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!sdd.hp.com!think.com!yale.edu!cmcl2!panix!alexis
From: alexis@panix.uucp (Alexis Rosen)
Newsgroups: comp.unix.aux
Subject: Re: Major problems with A/UX serial drivers?
Message-ID: <1991Jun28.014029.26566@panix.uucp>
Date: 28 Jun 91 01:40:29 GMT
References: <1991Jun26.153544.1186@panix.uucp> <1991Jun27.043913.2744@deadzone.uucp>
Organization: PANIX - Public Access Unix Systems of NY
Lines: 28

marcelo@deadzone.uucp (Marcelo Gallardo) writes:
>alexis@panix.uucp (Alexis Rosen) writes:
>>And do any
>>other A/UX sites which use serial I/O ever see problems like this?
>
>	I've experienced similar problems as well (although they aren't
>	happening as often now). But I never had the patience to sit and
>	wait to see if the port ever came back to life even for a
>	moment. 

The problems start small, at least sometimes. So for a while, you wonder
whether you're just not hitting the keyboard keys hard enough.

>	I had noticed that this generally happened when two precesses
>	tried to grab the port at the same time, or even when the port
>	was being used, and your UUPOLL script (wonderful script BTW)
>	tried to access the port.

(Thanks!) Could you go into more detail on this? The whole point of that
script was to _not_ do any damage if something else owns the port that the
script is trying to use. If that weren't the case here, this system would
be completely unusable- we're dialing in and out all the time.

---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NY
alexis@panix.com
{cmcl2,apple}!panix!alexis