Re: [U2] BP file ownership problem (linux)
Scott Ballinger wrote: What happens is that after user XXX edits a program, since the owner:group gets changed to XXX:XXX no one else can update that program until either XXX or someone as root chowns the file back to the uv group. This happens with all editors: ED, WED, etc. Is there a Universe setting or user setting that will prevent changing the owner and group setting on a file after editing it? (UV 10.1.4, RHEL 3). You have a couple of options. You can either make the uv group the primary group for the programming staff in /etc/passwd, or you can: chmod g+s BP The latter will force any files created under the BP directory to retain the same group ownership as the BP directory, regardless of user group settings. -John -- John Hester System Network Administrator Momentum Group Inc. (949) 833-8886 x623 http://memosamples.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] BP file ownership problem (linux)
Scott, Are all the people modifying the program a member of the uv group? When I change a source program, it sets my account as the owner, and the group to the group I'm a member of (which is the same group as all the programming staff.) Drew Scott Ballinger wrote: After editing a program in BP the owner and group of the file gets changed to user:user. This didn't use to be problem, as all programs in BP were set to 666, but now that we have implemented a minimal level of security, the BP programs are set to 664 with owner and group typically set to user:uv (the programming staff has membership in the uv group). What happens is that after user XXX edits a program, since the owner:group gets changed to XXX:XXX no one else can update that program until either XXX or someone as root chowns the file back to the uv group. This happens with all editors: ED, WED, etc. Is there a Universe setting or user setting that will prevent changing the owner and group setting on a file after editing it? (UV 10.1.4, RHEL 3). Thanks, Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- -- Drew Henderson There are two types of people - Dir. for Computer Center Operations those who do the work and those [EMAIL PROTECTED] who take the credit. Try to be in the first group, there is 110 Ginger Hall less competition. Morehead State University Indira Ghandi Morehead, KY 40351 Phone: 606/783-2445 Fax: 606/783-5078 -- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] BP file ownership problem (linux)
Thanks John, your second option was exactly what I was looking for. I had changed everyone's primary group to uv as an interim fix, but didn't feel that was the optimal solution. Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] BP file ownership problem (linux)
Sounds like you need to set UMASK in the LOGIN paragraph. I keep things pretty simple myself. I keep all users in one group. I keep the home directory in the main account and everyone shares the same UMASK. The only things I lock up is the BP files, dictionaries and paragraphs in the VOC. I do that by pointing all paragraphs to a PROD.VOC which only I can touch. Anthony -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ballinger Sent: Wednesday, June 29, 2005 3:31 PM To: u2-users@listserver.u2ug.org Subject: [U2] BP file ownership problem (linux) After editing a program in BP the owner and group of the file gets changed to user:user. This didn't use to be problem, as all programs in BP were set to 666, but now that we have implemented a minimal level of security, the BP programs are set to 664 with owner and group typically set to user:uv (the programming staff has membership in the uv group). What happens is that after user XXX edits a program, since the owner:group gets changed to XXX:XXX no one else can update that program until either XXX or someone as root chowns the file back to the uv group. This happens with all editors: ED, WED, etc. Is there a Universe setting or user setting that will prevent changing the owner and group setting on a file after editing it? (UV 10.1.4, RHEL 3). Thanks, Scott Ballinger Pareto Corporation Edmonds WA USA 206 713 6006 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.0/27 - Release Date: 6/23/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.0/27 - Release Date: 6/23/2005 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
