Jerry Feldman wrote:
Greg Wallace wrote:
Is this a group or permission problem? Maybe the default permissions should be 600? Then you wouldn't necessarily end up with a gazillion groups that may not have any real usefulness. That's one way around the problem, which I mentioned earlier. As for multiple groups, there are needs for them. For example in a work environment, where there are several projects, each with it's own group of people. There may be some who work in more than one group. Multiple groups pose no problems. For each project, you add the user ids or each member of that group. When one of these users wants to work within a
On Thursday 25 August 2005 8:18 am, James Knott wrote: project, he/she may use the newgrp(1) command to set the effective group to the desired group.
In general, out of the box, each new user is set up as a member of the users group. If I want to work on a project (say SL), if I am a member of the SL group, all I need to do is: newgrp SL I am now effectively in the group SL, and a new shell process is spawned.
Actually, a better way, is to add a user to the group and apply the sticky bit to the group directory. This way, the user has group access, immediately after logging on and any files created in the group directory can be accessed, according to group priviledges. Also, if you use that newgrp command, what happens when you return to your home directory and create a file there, while still a member of that other group? You've now created a file with group permissions, that you hadn't intended.