> I am not really certain if I understand this. > Is this a command "qpasswd". > Do i need to place the sticky bit on the directory and not the file? > This may all be moot because I am doing this through Samba. Does that > make a difference? Do I need to add something to my samba configs or to > my smbpasswd. > I also noticed that in the same directory which I have set the group to > "staff" and the user to "root", that when someone places a file or > creates a folder then it becomes theirs - IE user and group is the > person who created it and no one else can access it or modifiy it. I do > not want to make this directory a "public" directory just for the one > group. > Thank you all > Doug > > -----Original Message----- > From: jesse jacobs [mailto:[EMAIL PROTECTED]] > Sent: Friday, November 22, 2002 2:06 AM > To: [EMAIL PROTECTED] > Cc: Simpson, Doug > Subject: Re: sticky bit > > > >> I have a Linux 7.3 box that holds an ACT! database. When someone >> accesses the database they become the owner and group of a certain >> file - *.alf When thia happens no one else can access the data base >> abdthey receive an error that says some process is held open. So, I >> go back in and chgrp and chown. >> How can I stop this from happeing? >> Will setting the sticky bit help? >> Doug >> >> >> >> -- >> redhat-list mailing list >> unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe >> https://listman.redhat.com/mailman/listinfo/redhat-list > > Hey bud you're on the right track just use the sticky group bit and make > a secondary group for the db and all intended users. > ie. > qpasswd dbm > chown <primary user>.dbm <path to DB> > chmod 2775 <path to DB> > > In this fashion anyone who's a member of the dbm group has complete > access. When finished the group is set to dbm for any and all > files/dirs within. > > -- > Jesse Jacobs, Supa' Noob :)
First, yes gpasswd is a command(very old, must dust off kb prior to use:) ) This allows the admin to set a passwd on the group so users can elect to join the group by supplying the passwd for that group. If your users do not have shell access, you'll have to add them(Just tryin to save ya some work :) ). When dealing with acls the joy and pain of samba is that there are actually 2 acls in effect: the smb acl (ie. create mask = ????, directory mask = ????) and the OS acl (the actual permissions assigned by you to the fs/dir/file). Samba will not elevate permissions that are not available to the OS.(i.e. if a dir has 0770 as the permissions then this is the extent of the allowed permissions assigned by samba. (i.e.Your create mask param will only be able to allocate r/w/x to the user and group bits but not other bits.) Once your group "staff" has been created and assigned issue: chown -R root.staff <path to DB dir> chmod -R 2770 <path to DB dir> -- Jesse Jacobs, Supa' Noob :) -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
