Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!mimsy!mojo!cyliao
From: cyliao@eng.umd.edu (Chun-Yao Liao)
Newsgroups: comp.sys.next
Subject: More on Device Busy
Message-ID: <1991May25.004939.8691@eng.umd.edu>
Date: 25 May 91 00:49:39 GMT
Sender: news@eng.umd.edu (C-News)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 18

I've got a few responses, but most of them had same problem.
It seems to me that the problem occurs with 040+2.1.

Now, it happens always everytime when I mount an OD. I quit ALL
processes except workspace manager... didn't help.
I even used ofiles, an utility ported by Vic Abell, to show all
possible processes left on OD directories... no luck, none of the 
process has anything to do with OD, but the OD just desn't umount...

any other with OD experienced the same prob? The only way I can
correct the prob is power down and up... which is not very nice...


--
cyliao@bagend.eng.umd.edu       o Q. Who am I?
      NeXTmail o.k.       	o A. A NeXTed person with 320meg HD and OD
  I have MailService	        o    An Apple // guy
 and a 2400 modem w/o MNP	o    An airplane pilot (I hope)