Hi Tony: > That's true for primary groups, but if Bill needed to access files owned > by some other group, then you would have to add him to that group in > /etc/group. Then he would be able to access files owned by his primary > group (GID 500) and files owned by whatever other groups he's a member of, > as defined in /etc/group.
OK. Good. > A side effect of using the same primary GID for multiple users (defined in > /etc/passwd) is that they will be able to read/write each others personal > files by default, assuming the file is in an accessible directory. Yes, I understood that. In my case the users don't have any shell access. They do have guest ftp access so they are chrooted to their own home folder on login. And I'm using radius based group restriction authentication with this box which as far as I can tell keys on the primary group mapping and won't look up a "secondary" group. Apparantly ditto for ftpaccess guest behavior. So looks like I'm OK. Doing without the ability to have user's file access permissions span groups isn't a problem for me on this box. Just wanted to be sure I wasn't breaking something (that I use and don't know it <g>) by leaving off the userid on the group file entry with my adduser program. Thanks again for taking the time to help, Scott _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
