SunOS has the "fuser" command, which lists processes using a file or
file structure.
fuser /afs
should reveal what might be going on here.
You'll need to run this as root, as you have to open /vmunix.
-b.
On Wed, 11 Sep 1996, Joseph L Jackson wrote:
> There's a helpful clue hidden in the last message. The number inside the
> parens is actually the "errno" value set by the failing "mount()" call.
> On a Solaris machine, 16 translates to "device busy":
>
> [~] translate_et 16
> 16 ().16 = Device busy
> [~] grep 16 /usr/include/sys/errno.h
> #define EBUSY 16 /* Mount device busy */
>
> The errno values don't always match across different OSs, so you'll want
> to check on your SunOS 4.1.4 machine to be sure of the meaning.
>
> You get a "device busy" error when the /afs directory is in use already.
> Use the "mount" command to see if someone has already started AFS. Or
> perhaps someone NFS mounted /afs while you weren't looking. Also be sure
> that no one has their current working directory set to /afs when you
> start it up. That's all I can think of off the top of my head.
--
Brian W. Spolarich - ANS - [EMAIL PROTECTED] - (313)677-7311
Look both ways before crossing the Net.
