"Andrew Daugherity" <adaugher...@tamu.edu> writes: >> And I update the sharenfs option with "rw,ro...@100.198.100.0/24", >> it works fine, and the NFS client can do the write without error. >> >> Thanks. > > I've found that when using hostnames in the sharenfs line, I had to use > the FQDN; the short hostname did not work, even though both client and > server were in the same DNS domain and that domain is in the search > path, and nsswitch uses DNS for hosts (read: 'ping client1' works fine, > as does 'mount server:/export/fs /mnt' from client1). > > Perhaps it's because I left the NFSv4 domain setting at the default. > (I'm just using NFSv3, but trying to come up with an explanation. In > any case, using the FQDN works.)
if you wanted to add more would it just be separated with a comma: sharenfs=on,rw,ro...@198.xxx.xxx.xxx,userna...@192.xxx.xxx.101 or do you have to add the rw, for each one too: sharenfs=on,rw,ro...@198.xxx.xxx.xxx,rw,userna...@192.xxx.xxx.102 Is any of that syntax right? _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss