Hi,
I am using suse 9.0 on cluster machines
(runnnig nfs servers) and on client machine.
I am also using virtual ip so that nfsserver
is transparently failed over to other machine.
when nfs server fails over and sm-notify
notifies the client , client does not reclaim
locks , reason being that nfsserver sends
notification using its base ip address and not
virtual ip
Client does not find this base ip in its monitored
host list(as it access nfs server using virtual
ip)
This works on Redhat systems as rpc.statd has -n
option using which statd on server always
communicate with client using virtual ip
(rpc.statd -n <virtual ip>)
Also let me know if rpc.statd is going to be part
of Suse later or is sm-notify going to be modified
to give full functionality of rpc.statd
Any suggestions would be appreciated
Thanks,
kiran
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs