NFSv4

["J.A. Magallón" <jamagallon@ono.com>]

Hi all...

First of all, kudos for new nfs-utils. Now, nfs4 works automagically and
like a charm.

And now the hard part, some questions:

- I have read that nfs4 includes in the server the locking protocol, no
  need for separate lockd. But in my servers, it seems it is still running:

root      2198     2  0 Feb18 ?        00:00:00 [nfsiod]
root     23501     2  0 01:01 ?        00:00:00 [nfsd4]
root     23502     2  0 01:01 ?        00:00:00 [nfsd]
root     23503     2  0 01:01 ?        00:00:00 [nfsd]
root     23504     2  0 01:01 ?        00:00:00 [nfsd]
root     23505     2  0 01:01 ?        00:00:00 [nfsd]
root     23506     2  0 01:01 ?        00:00:00 [nfsd]
root     23507     2  0 01:01 ?        00:00:00 [nfsd]
root     23508     2  0 01:01 ?        00:00:00 [nfsd]
root     23509     2  0 01:01 ?        00:00:00 [nfsd]
root     23500     2  0 01:01 ?        00:00:00 [lockd]

  Is there any problem with it ? I suppose (correct me if I'm wrong)
  that this kernel lockd will only serve for v2 or v3 mounts,
  that locking for client nfs4 mounts will go through nfsd4.
  Is that right ?

- Why is there only 1 instance of v4 daemon ?

- Is there any page describing the advantages of v4 ? I will have to
  convince the department admin to activate v4 in his solaris boxen...;)

TIA

Notes: kernel is 2.6.33-rc8, nfs-utils are 1.2.2.

-- 
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free