Re: [patch] fix statd -n

[Wendy Cheng <s.wendy.cheng@gmail.com>]

Janne Karhunen wrote:
> On Mon, May 5, 2008 at 10:59 AM, Wendy Cheng <s.wendy.cheng@gmail.com> wrote:
>
>   
>>> In any case, if there's still a legimate use case for -n, even if it's
>>> not great, we should err on the side of fixing it just to save problems
>>> for anyone with an existing working setup.
>>>
>>>       
>>  Simpler code and consolidated logic flow are always better - would like to
>> vote for its deletion.
>>     
>
> So the solution would be to use -H with a script that
> does sm-notify with user specified name (-v)? Kernel
> name can't be used directly as it might migrate to
> node that has different name.
>
>
>   
No. "-H" is only for different export (server IP) interfaces. Say server 
has 10.1.1.1 and 10.1.1.2 as NFS export interfaces. If 10.1.1.1 is 
migrated but 10.1.1.2 stays, you would like to notify the nfs clients 
coming in from 10.1.1.1 but not the clients from 10.1.1.2, you need to 
structure your sm directory seperately. That is the usage of "-H" (to 
allow admin to organize client IPs).

For a single export IP interface like you have (even you have a seperate 
hostname), ignore "-H". I believe "sm-notify -v" should be enough - 
otherwise we have bugs - i.e., sm-notify should be part of your nfsd 
bring-up script.

-- Wendy