[OpenIndiana-discuss] setting up nfs4 from scratch

[Harry Putnam]

Mark <mark0x01 at gmail.com> writes:

[...] Thanks for the very complete instructions. 

  On my linux distro [debian wheezy] I see this in /etc/idmapd.conf

  # set your own domain here, if id differs from FQDN minus hostname
  # Domain = localdomain

And since `hostname -f (-f means show fqdn) shows my full
hostname.local.domain  I guess that can stay commented.

> nfs3 does not require the domain settings.
> I use both nfs3 and nfs4, but GID/UID issues and ACLS can be tricky,
> especially if you run cifs on the same file system as I do.

So are you saying that even with the settings you posted... you still
have trouble with windows boxes over of cifs?  Or do you mean your
posted settings will avoid that happenstance?

I'm trying just to run nfs4 so maybe it will not effect me.

Oh, and what chmod cmd do you use on any shares to be shared with
windows platforms?  In the past, for cifs, I've used:

   chmod -R A=everyone@:full_set:fd:allow

But on one of the googled pages:
(http://www.bfccomputing.com/2011/03/15/creating-a-permission-free-share-with-zfs-acls-and-nfsv4/)

I found while working on this showed a
really lengthy chmod cmd:

  (wrapped for mail)

  /bin/chmod A=everyone@:read_data/list_directory/write_data/add_file/\
  append_data/add_subdirectory/read_xattr/write_xattr/execute/delete_child/\
  read_attributes/write_attributes/delete/read_acl/write_acl/write_owner/\
  synchronize:file_inherit/dir_inherit:allow

Is something like that really necessary or does the shorter one cover
the same stuff with :full_set:fd:allow?