Tom Haynes wrote: > Kyle McDonald wrote: >> Functionally what's the difference between allowing root nfs access >> with root=*, and allowing it with anon=0? >> >> I have a JumpStart filesystem that was shared through /etc/dfs/dfstab >> with '-o sec=sys,ro,anon=0'. On this file system there are files that >> are owned by root and mode 600. During jumpstart these files can be >> copied fine. >> >> WHen I was converting to use sharemgr, at first I missed the fact >> that it has an 'anon=0' option, and decided to used 'root=*' instead. >> For some reason this broke things, those same files couldn't be copied. >> >> Switching back to 'anon=0' fixed things again. >> >> Why? >> >> The onnly difference I can see is that root= allows a list of hosts, >> but when used with an * it should work the same as anon=0 right? >> >> > > You can't use root with a '*'. Then the sharemgr man page needs updating. :)
It says that the syntax is root=access_list, where an access_list is any of: *, hostname, netgroup, domainname.suffix, or network. > > The real difference is that anon does not have to mean a root mapping > and what happens if you > mix the two. I knew there were other ways to be anonymous, but in my case it seemed the two should be equivalent. > > > This should give you a start at understanding the interactions. > That's what I thought, but didn't realize that the root=* wasn't allowed. I've got other complaints about sharemgr though, but I'll save them for another thread (or maybe a bug report.) -Kyle
