RE: [Samba] Upgrade & directory permissions
That's correct. Just play with the umask setting in the smb.conf file so that the end result is what u need. That is what happened in our situation as well. If you want it to be 770.. and u notice its ending up at 755, play with the smb.conf umask to obtain the value of 770. Jose -Original Message- From: EXT-Auleta, Michael [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 2:29 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [Samba] Upgrade & directory permissions I don't want to open up the directory & file permissions for security reasons. We set the gid bit on the directories so any new files or directories that get created underneath get created with the correct group ownership. The permissions on the directories are 770 and the users are members of the group owner of the directories. -Original Message- From: Jose Martinez [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 2:03 PM To: EXT-Auleta, Michael; [EMAIL PROTECTED] Subject: RE: [Samba] Upgrade & directory permissions What is the umask setting in the smb.conf file for your shares. I know I had to play with the umask setting to get it to work on mine. Sometimes, the umask setting doesn't even make sense, however I just set them to what I needed the end result to be. Not sure if the /etc/bashrc setting plus this setting is what is causing my weird umask setting, but its all working like I like it now. In addition, we have a different type of setup where the user owns his home directory, however the admins group is the group owner of the directory, not the users group. So every 20 minutes I have a quick script that goes out there and changes the group ownership of any new file created to the admins group for group for group ownership. We do this so that the admins can modify any file under the home directories and profiles. Example of umask setting: [Profiles] path = /home/profiles browseable = no guest ok = yes writable = yes create mask = 707 nt acl support = yes profile acls = yes Jose -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EXT-Auleta, Michael Sent: Tuesday, April 20, 2004 1:30 PM To: [EMAIL PROTECTED] Subject: [Samba] Upgrade & directory permissions I've just upgraded the version of Samba we're running from 2.2.2 to 3.0.2a and am seeing an issue with permissions on directories. Users can still map the shares that are set up, but cannot access the directories within those shares. This is also not consistent; it's not happening to all users. Our environment: Samba 3.0.2a Domain Authentication to a Win2K server No Winbind Solaris 8 on a Sun E3000 server I'm inclined to back out the upgrade, but if there's a quick fix I'd prefer to implement that. Any ideas? Mike Mike Auleta Boeing IDS, Philadelphia 610-591-3916 Who's the more foolish, the fool or the fool who's following him? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Upgrade & directory permissions
I don't want to open up the directory & file permissions for security reasons. We set the gid bit on the directories so any new files or directories that get created underneath get created with the correct group ownership. The permissions on the directories are 770 and the users are members of the group owner of the directories. -Original Message- From: Jose Martinez [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 2:03 PM To: EXT-Auleta, Michael; [EMAIL PROTECTED] Subject: RE: [Samba] Upgrade & directory permissions What is the umask setting in the smb.conf file for your shares. I know I had to play with the umask setting to get it to work on mine. Sometimes, the umask setting doesn't even make sense, however I just set them to what I needed the end result to be. Not sure if the /etc/bashrc setting plus this setting is what is causing my weird umask setting, but its all working like I like it now. In addition, we have a different type of setup where the user owns his home directory, however the admins group is the group owner of the directory, not the users group. So every 20 minutes I have a quick script that goes out there and changes the group ownership of any new file created to the admins group for group for group ownership. We do this so that the admins can modify any file under the home directories and profiles. Example of umask setting: [Profiles] path = /home/profiles browseable = no guest ok = yes writable = yes create mask = 707 nt acl support = yes profile acls = yes Jose -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EXT-Auleta, Michael Sent: Tuesday, April 20, 2004 1:30 PM To: [EMAIL PROTECTED] Subject: [Samba] Upgrade & directory permissions I've just upgraded the version of Samba we're running from 2.2.2 to 3.0.2a and am seeing an issue with permissions on directories. Users can still map the shares that are set up, but cannot access the directories within those shares. This is also not consistent; it's not happening to all users. Our environment: Samba 3.0.2a Domain Authentication to a Win2K server No Winbind Solaris 8 on a Sun E3000 server I'm inclined to back out the upgrade, but if there's a quick fix I'd prefer to implement that. Any ideas? Mike Mike Auleta Boeing IDS, Philadelphia 610-591-3916 Who's the more foolish, the fool or the fool who's following him? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Upgrade & directory permissions
What is the umask setting in the smb.conf file for your shares. I know I had to play with the umask setting to get it to work on mine. Sometimes, the umask setting doesn't even make sense, however I just set them to what I needed the end result to be. Not sure if the /etc/bashrc setting plus this setting is what is causing my weird umask setting, but its all working like I like it now. In addition, we have a different type of setup where the user owns his home directory, however the admins group is the group owner of the directory, not the users group. So every 20 minutes I have a quick script that goes out there and changes the group ownership of any new file created to the admins group for group for group ownership. We do this so that the admins can modify any file under the home directories and profiles. Example of umask setting: [Profiles] path = /home/profiles browseable = no guest ok = yes writable = yes create mask = 707 nt acl support = yes profile acls = yes Jose -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of EXT-Auleta, Michael Sent: Tuesday, April 20, 2004 1:30 PM To: [EMAIL PROTECTED] Subject: [Samba] Upgrade & directory permissions I've just upgraded the version of Samba we're running from 2.2.2 to 3.0.2a and am seeing an issue with permissions on directories. Users can still map the shares that are set up, but cannot access the directories within those shares. This is also not consistent; it's not happening to all users. Our environment: Samba 3.0.2a Domain Authentication to a Win2K server No Winbind Solaris 8 on a Sun E3000 server I'm inclined to back out the upgrade, but if there's a quick fix I'd prefer to implement that. Any ideas? Mike Mike Auleta Boeing IDS, Philadelphia 610-591-3916 Who's the more foolish, the fool or the fool who's following him? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Upgrade & directory permissions
I've just upgraded the version of Samba we're running from 2.2.2 to 3.0.2a and am seeing an issue with permissions on directories. Users can still map the shares that are set up, but cannot access the directories within those shares. This is also not consistent; it's not happening to all users. Our environment: Samba 3.0.2a Domain Authentication to a Win2K server No Winbind Solaris 8 on a Sun E3000 server I'm inclined to back out the upgrade, but if there's a quick fix I'd prefer to implement that. Any ideas? Mike Mike Auleta Boeing IDS, Philadelphia 610-591-3916 Who's the more foolish, the fool or the fool who's following him? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
