DISREGARD, please delete thread. Looks like this indeed is the default behavior.
During testing, it was discovered that any file created under a directory owned by wheel will have the group id set to wheel by default; similar to having the group id sticky bit set. This should not be the normal UNIX file system behavior. Usually if a user has write permission to the directory, the file created by that user should have the user's uid and the user's primary group id.
Is this just a bug or is this the preferred behavior for FreeNAS/FreeBSD/ZFS? Needless to say, this breaks a lot of things when you're sharing a directory with many users (/tmp for example), but wanting each user to maintain access to only their individual files.
Not to mention files will lose their original group owner info if you're using FreeNAS as a backup server.
????
During testing, it was discovered that any file created under a directory owned by wheel will have the group id set to wheel by default; similar to having the group id sticky bit set. This should not be the normal UNIX file system behavior. Usually if a user has write permission to the directory, the file created by that user should have the user's uid and the user's primary group id.
Is this just a bug or is this the preferred behavior for FreeNAS/FreeBSD/ZFS? Needless to say, this breaks a lot of things when you're sharing a directory with many users (/tmp for example), but wanting each user to maintain access to only their individual files.
Not to mention files will lose their original group owner info if you're using FreeNAS as a backup server.
????
Last edited:
