-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14-Jun-2002/12:33 -0500, "scott.list" <[EMAIL PROTECTED]> wrote: > >I have found that ommiting the group's comma separated user name list >seems to have no effect. > >My question is what uses or looks at the username list appended to the >group line in the group file i.e.: > >engr::500:bill,tom,jim >acct::600: >fact::700: > >It looks to me that as long as bill, tom, and jim's password line >looks like: > >bill:passwd:uid:500:Bill Jones:........ > >,then their group is assigned correctly and their group related stuff >works as it should even though the group file line does not contain >their userid's as in:: > >engr::500:
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. 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. Tony - -- Anthony E. Greene <mailto:[EMAIL PROTECTED]> OpenPGP Key: 0x6C94239D/7B3D BD7D 7D91 1B44 BA26 C484 A42A 60DD 6C94 239D AOL/Yahoo Chat: TonyG05 HomePage: <http://www.pobox.com/~agreene/> Linux. The choice of a GNU generation <http://www.linux.org/> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Anthony E. Greene <mailto:[EMAIL PROTECTED]> 0x6C94239D iD8DBQE9Co+dpCpg3WyUI50RAjY9AJ9IsZpoPTkoJzb2Xi5tg9BeTQXMYgCfW8bX vq9MX9wM0f8B3tosEnsiUP0= =6CMT -----END PGP SIGNATURE----- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
