LinuxSA Mailing list archives

  From: Adam Smith <adam.smith@sageautomation.com>
  To  : LinuxSA \(E-mail\) <linuxsa@linuxsa.org.au>
  Date: Wed, 15 May 2002 09:40:28 +0930

Locked port

Hello,


I appear to have locked cuaa0.

I did some looking around to see how I could unlock it, and learned (of
course) that a program can lock the port by setting a lock file in
/var/lock, the file in this case was called LCK..cua1.  (From
http://www.tldp.org/HOWTO/Serial-HOWTO-12.html)

Or at least I was assuming it was..  I couldn't see the correlation
between cuaa0 and "cua1" because I would assume "cua1" was referring to
"com2".  Regardless of that, the PID within the lock file had already
been terminated.  I removed this lock file and the port is still busted.

Running "tip com1" tells me "all ports busy" and "tip com2" shows a free
port.

How do I free up "com1" ?


--
Adam Smith
IT Officer
SAGE Automation Ltd

adam.smith@sageautomation.com
http://www.sageautomation.com

Phone:   (08) 8276 0703
Fax:     (08) 8276 0799
Mobile:  0414 895 273

Dog for sale: Eats anything and is fond of children.


-- 
LinuxSA WWW: http://www.linuxsa.org.au/  IRC: #linuxsa on irc.linux.org.au
To unsubscribe from the LinuxSA list:
  mail linuxsa-request@linuxsa.org.au with "unsubscribe" as the subject