| Title: | SunNet - the defacto distributed system standard |
| Moderator: | CVG::PETTENGILL |
| Created: | Mon Jun 02 1986 |
| Last Modified: | Fri May 16 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 479 |
| Total number of notes: | 1270 |
Hello,
a customer has the following configuration:
1 server that exports a directory called /prova/dati
1 client that mounts the remote directory
on the client runs a program that created and update several files.
Some times the server is turn down while the client still has the
remote directory mounted.
Is there a fast way to know that the remote server is actualy unavailable?
If he issues a write on a file, non longer served, he sees the message:
NFS3 server bluff not responding still trying
and the command doesn't return.
Digital Unix 4.0
Thanks,
Gea
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 476.1 | Re: how to get server status | QUABBI::"werme@zk3.dec.com" | Fri Apr 11 1997 00:36 | 17 | |
voci@mlncsc.enet.dec.com writes: >Title: how to get server status > Is there a fast way to know that the remote server is actualy unavailable? My usual recommendations are "ping <server>" and "rpcinfo -p <server>". If you want to see if NFS is acutally willing to talk back to you, then "rpcinfo -u <server> nfs 3" is good. Ping tells you if the server is up at all, rpcinfo -p tells you if portmap is running and what has registered with it, rpcinfo -u or -t actually calls the service. -- <> Eric (Ric) Werme <> This space under reconstruction <> <> <werme@zk3.dec.com> <> <> [posted by Notes-News gateway] | |||||
| 476.2 | from C program? | MLNCSC::VOCI | Fri Apr 11 1997 07:43 | 8 | |
Do you know if it is possible to have the same information from a
system call that I can be used by a C program?
I've tested the stat* routines with no success.
Thanks,
Gea
| |||||
| 476.3 | KITCHE::schott | Eric R. Schott USG Product Management | Sat Apr 12 1997 13:21 | 7 | |
Hi You could mount soft rather than hard, and be sure you application checks I/O status returns on I/O calls, then you would find out within the NFS timeout. | |||||