In a message dated: Thu, 12 Oct 2000 09:32:58 EDT
Matt Herbert said:
>> Try restarting mountd?
>
>Nope. I'm hesitant to do that because there are about 30 hosts who
>have nfs mounts from the server, and the last time I tried to re-start
>the nfs processes, I was unable to get the services running again, and
>ended up having to reboot.
You should be able to stop and start mountd on the server without any
problems. Stopping mountd on the server should have no adverse effect on the
server, just the clients, and as soon as it's started again, the clients
should fix themselves (worst case you might need to manually fix a client),
but there shouldn't be anything here that would warrant the reboot of the
server.
>yes. NIS.
>
>> What's you're nsswitch.conf file say?
>
>hosts: files nisplus nis dns
>(I assume this is the line your interested in)
If you're not using nisplus or DNS, then I would remove them from both the
server and client versions of this file. If all you're using is NIS, then
you want something like:
hosts: files nis or hosts: nis files
>The network is working fine, everybody can resolve everybody
>else's name and ping each other without problems. In fact on
>the system trusty (which is a Solaris8 box) I can mount the other
>two shares (/disk/share1 and /disk/share2) I just can't mount
>the one I want (/disk)!
I don't know. There seems to be some kind of permissions problem somewhere.
--
Seeya,
Paul
----
I'm in shape, my shape just happens to be pear!
If you're not having fun, you're not doing it right!
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
