Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!ncar!gatech!udel!princeton!deadzone!marcelo
From: marcelo@deadzone.uucp (Marcelo Gallardo)
Newsgroups: comp.unix.aux
Subject: Re: Major problems with A/UX serial drivers?
Message-ID: <1991Jun30.201839.6549@deadzone.uucp>
Date: 30 Jun 91 20:18:39 GMT
References: <1991Jun26.153544.1186@panix.uucp> <1991Jun27.043913.2744@deadzone.uucp> <1991Jun28.014029.26566@panix.uucp>
Organization: DeadZone * A/UX 2.0.1 SVR2 * 609-443-4762
Lines: 27

alexis@panix.uucp (Alexis Rosen) writes:

>>	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.
	
	When I would grab the tty1 port (to call out via cu), and UUPOLL
	would try to grab the port, it would sometimes freeze up the
	system. It was as if it didn't see the LCK file. I hardcoded the
	LCK check into the script, and I haven't had a problem since.

	I don't know why it was "ignoring" the LCK as you had it
	written, since it obviously seems to work for you, but it didn't
	here. It would then try to set the port, and that's when things
	got messy.

-- 
Marcelo Gallardo			marcelo%deadzone@princeton.edu
Test and Evaluation Specialist		...!princeton!deadzone!marcelo
Princeton University			marcelo@sparcwood.princeton.edu
Advanced Technologies and Applications		(609) 258-5661