Hi,

Today I was checking the system and I tried to run the df comand and it
lists but doesnt exit out; it hangs.

I also tried to run who -r to see the run level. That command doesnt
produce any results as it used to show run level 3

Lastly what prevents the user from running "find / -name protocols
-print"?
How to correct the behavior?
I run as root it works fine.

Thanks
Joe

[ Post a follow-up to this message ]

Joe wrote:
> Hi,
>
> Today I was checking the system and I tried to run the df comand and it
> lists but doesnt exit out; it hangs.

I've seen that behavior with df on a system which has an NFS-mounted
filesystem, when the server is unavailable. It'll list local disks
first, then sit there waiting for the response. It usually comes back
with something like "<nfsserver> not responding," though, once it
timesout.  Did you let df hang for a while? ISTR that 600 seconds is
the timeout for TCP.

> [...]

> Thanks
> Joe

Regards,
Jon

[ Post a follow-up to this message ]

No; I see the NFS mounts listed though

Jon wrote:
> Joe wrote: 
>
> I've seen that behavior with df on a system which has an NFS-mounted
> filesystem, when the server is unavailable. It'll list local disks
> first, then sit there waiting for the response. It usually comes back
> with something like "<nfsserver> not responding," though, once it
> timesout.  Did you let df hang for a while? ISTR that 600 seconds is
> the timeout for TCP.
> 
> 
>
> Regards,
> Jon

[ Post a follow-up to this message ]

On Fri, 08 Dec 2006 08:51:02 -0800, Joe wrote:
[vbcol=seagreen]
> No; I see the NFS mounts listed though
>
> Jon wrote: 

Run mount to get a list of the mounted filesystems and compare it with
your partial df output to see which FS is causing the issue.

JohnK

[ Post a follow-up to this message ]