Sure, but it's really straightforward: 0,5,10,15,20,25,30,35,40,45,50,55 * * * * chown -R user1:group1 /zpool1/test/share2/* 2> /dev/null ; chmod -R g+w /zpool1/test/share2/* 2> /dev/null
Here's the thing: There's no way that it was a hard/soft link. I know what those are and I haven't linked anything from those filesystems. When I was trying to troubleshoot this I discovered that on the system that was >mounting< the NFS share I could change the permissions at the mount point (which correlated to /share2) and it would mess up the CIFS share. Yes, setting permissions on the >mounting< system would cause the problem to happen. To clarify how odd that is: /zpool1/test/share2 is mounted on a web server at /mount/point. Going to /mount/point as root and chowning * caused the issue to happen with /zpool1/test/share1. This is reproducible, by the way. I can cause this to happen again, right now if I wanted to... Another thing: I checked the ownership and perms on /zpool1/test/share1. ls -dV showed no change in the ACLs than from what I had set. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
