It seems like our problem is not a commom one and surprisingly I
received only one(!) response about it.
In case anybody thinks of anything, please mail me.
Since we cannot reproduce the problem, we will try Ron's solution if it
Ron is probably correct, we were also suspecting of some type of a
caching "malfunction" but couldn't pin-point it.
If it happens and we fix it I will post.
We have about five systems running Solaris 2.5.1 in a NIS+ environment,
with NFS 3.0. Last week, we suddenly could not access any remotely
mounted file-system from the NIS+ master server.
We would 'cd' to a directory and we would just hang. When tried to
CTRL-C we were un-hanging but getting a "bad directory" error message....
We did stop/start the automounter -- no change.
Interestingly enough, while the problem was present, we
were able to establish a new remote mount with no problem.
We resolved the problem by rebooting the NIS+ master server.
RESPONSE by Ronald W. Henderson
You may have been burned by the name service cache deamon: 'nscd'.
Caching incorrect info...
Next time try flushing its cache. The only way I know how to do this is
by stopping and restarting the daemon: (/etc/init.d/nscd stop ;
ESA Project Scientist Team/CDS Operations
NASA Gooddard Space Flight Center
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:43 CDT