From owner-freebsd-questions Wed Jun 4 07:57:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA02144 for questions-outgoing; Wed, 4 Jun 1997 07:57:56 -0700 (PDT) Received: from odin.visigenic.com (odin.visigenic.com [204.179.98.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA02138 for ; Wed, 4 Jun 1997 07:57:53 -0700 (PDT) Received: from VSI48 (vsi48.visigenic.com [206.64.15.185]) by odin.visigenic.com (Netscape Mail Server v2.02) with SMTP id AAA22741 for ; Wed, 4 Jun 1997 07:57:11 -0700 Message-Id: <3.0.32.19970604075746.00a02ec0@visigenic.com> X-Sender: toneil@visigenic.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 04 Jun 1997 07:57:47 -0700 To: questions@FreeBSD.ORG From: "Tim Oneil" Subject: Re: Can't umount /cdrom Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 12:06 PM 6/4/97 +0200, you wrote: >> I have a problem using one of my compact disks. >> When I try umount it system responds: Device busy >> but no one at this time using CD. >> Any suggestions? > >You probably are cd'd to the directory or subdirectories >of /cdrom. Or you have started a program from the CD. Yep. I've found, after a little patient searching, that when this happens to me there is always some little out of the way process that has the cdrom open. You just have to search through all your terminals until you find out which one it is. What I do much of the time is have X running tkdesk in one terminal, look at the cdrom with the filemgr, then go to a xterm or even another console and completely forget about the filemgr. Then I go to umount the rom and *bam*, locked. Would it be possible to write an X app that will constantly show the lock status of a cdrom device, maybe show what process has the lock? That would be useful. -Tim