From owner-freebsd-questions@FreeBSD.ORG Thu Jun 24 16:47:59 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AFD216A4CE for ; Thu, 24 Jun 2004 16:47:59 +0000 (GMT) Received: from ms-smtp-03.rdc-nyc.rr.com (ms-smtp-03-smtplb.rdc-nyc.rr.com [24.29.109.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65F0943D31 for ; Thu, 24 Jun 2004 16:47:56 +0000 (GMT) (envelope-from freebsd@toyingwithfate.com) Received: from toyingwithfate.com (66-108-61-89.nyc.rr.com [66.108.61.89]) i5OGld20017307 for ; Thu, 24 Jun 2004 12:47:39 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by toyingwithfate.com (8.12.9p1/8.12.9) with ESMTP id i5OGhXUE000682 for freebsd-questions@freebsd.org; Thu, 24 Jun 2004 12:43:48 -0400 (EDT) (envelope-from freebsd@toyingwithfate.com) Date: Thu, 24 Jun 2004 12:43:33 -0400 (EDT) Message-Id: <200406241643.i5OGhXUE000682@toyingwithfate.com> From: Will McCutcheon To: freebsd-questions@freebsd.org X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Scanned: clamd / ClamAV version 0.72, clamav-milter version 0.72 on toyingwithfate.com X-Virus-Status: Clean Subject: Unlocking devices? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2004 16:47:59 -0000 Quick and (maybe) easy question. I spend a lot of time using serial consoles on FreeBSD and for a variety of reasons am constantly ended up with serial ports that are "locked" or "in use", even when there's no program attached to them anymore (cu or minicom getting killed can reliably cause this). I understand why this happens so I'm not complaining about it, but I wondered is there some way to force the system to free up /dev/cuaa0 without restarting? Thanks for your help! W