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 :) -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list