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
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
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
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
