site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Mutt/1.4i On Fri, Sep 17, 2004 at 07:52:37AM +0000, GirisH wrote:
Portmap service must be running in order to make RPC calls.
More importantly, portmap needs to be running before any RPC services are started so that the servers can register their ports with portmap so clients can be told what ports to connect to.
After creating , modifying , deleting NFS share we restart mountd service using
killall -HUP mountd
When we try to access NFS share through NFS client sometimes portmap daemon goes into unstable state automatically.
Can you be more specific about the details of this "unstable state"?
Because of that when user try to mount NFS share from client machine mount command hangs up.Even if we try to restart portmap service NFS client can not mount the daemon, it gets hanged.
Restarting portmap is NOT a good idea, since that will cause all the current port registrations to be lost.
Most of the times after rebooting machine (Mac OS 10.3) portmap works properly and NFS client can mount NFS share.
That's probably because the startup scripts know how to start all the NFS server services in the correct order: portmap rpc.statd rpc.lockd mountd nfsd
Can you please suggest us why portmap service on Mac OS X 10.3 behaves like this?
What we can do so that portmap service should not get into unstable state?
Well, you already know that rebooting after making NFS export changes works. Yes, it's a big hammer... but it works. If the system was booted with NFS exports defined, all the services should be started properly. If you change your existing set of exports, then a "sudo killall -HUP mountd" should just work. "rpcinfo -p" can be used to check the state of portmap "showmount -e" can be used to check the state of your exports If everything looks OK and it's still not working, then perhaps it's time to start grabbing network packet traces with tcpdump. --macko _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com