From owner-freebsd-hackers  Sat Jul 22 17:06:49 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id RAA10516
          for hackers-outgoing; Sat, 22 Jul 1995 17:06:49 -0700
Received: from virgo.ai.net (virgo.ai.net [198.69.44.2])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA10508
          for <hackers@freebsd.org>; Sat, 22 Jul 1995 17:06:45 -0700
Received: from aries.ai.net (aries.ai.net [198.69.44.1]) by virgo.ai.net (8.6.11/8.6.12) with ESMTP id UAA10228 for <hackers@freebsd.org>; Sat, 22 Jul 1995 20:14:35 -0400
Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id UAA11243; Sat, 22 Jul 1995 20:06:30 -0400
Date: Sat, 22 Jul 1995 20:06:30 -0400 (EDT)
From: Network Coordinator <nc@ai.net>
To: hackers@freebsd.org
Subject: Problem w/ serial ports going busy.
Message-ID: <Pine.BSF.3.91.950722200422.11233A-100000@aries.ai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: hackers-owner@freebsd.org
Precedence: bulk


I have several cuaa ports set up to handle dial ins. At odd times the 
ports will just go busy [i.e. Kermit says, "Sorry, can't open connection: 
/dev/cuaa1: Device Busy"]

Nothing is running except getty on those ports [and when I kill getty the 
device doesn't get freed] and the modems are configured perfectly.

Any ideas [even dirty ways] of forcing the ports un-busy? I really hate 
having to reboot the machine to get things working.

Thanks,

-Jerry.