Permissions - explanation, please?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I found the problem I was having earlier and fixed it. I still don't understand it, so maybe someone can enlighten me. I created a group (kdev) in Yast and added my userid to it. This was also set to the group owner of a directory. Even so, I couldn't write to the directory. I finally did a "groups" command, and I saw that my userid did not reflect itself as belonging to "kdev" - even though Yast (and /etc/group) clearly showed that it was. This didn't change until I logged off and logged back in. I understand the system caching the group list for efficiency, but shouldn't the cache have been refreshed after I made the modifications? I thought Yast took care of that (obviously, I was wrong). Is there another way to force the groups list to be refreshed. Having to logoff - or reboot - is so ... Windows like. Would someone please enlighten me. Inquiring minds want to know. <g> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFAnpISjeziQOokQnARAmNdAJ9GGnAtbLTdlqtxgJpROohGb/jH8gCbBaBx /nAZl/uc7fG+bNZzUw3Pp6o= =eLYt -----END PGP SIGNATURE-----
The Sunday 2004-05-09 at 15:18 -0500, Michael Satterwhite wrote:
I finally did a "groups" command, and I saw that my userid did not reflect itself as belonging to "kdev" - even though Yast (and /etc/group) clearly showed that it was. This didn't change until I logged off and logged back in.
I understand the system caching the group list for efficiency, but shouldn't the cache have been refreshed after I made the modifications? I thought Yast took care of that (obviously, I was wrong). Is there another way to force the groups list to be refreshed. Having to logoff - or reboot - is so ... Windows like.
You do not need to reboot, but simply log off your user session, and log in again. Those settings are read when you log in, so the behaviour you describe is absolutely normal. -- Cheers, Carlos Robinson
participants (2)
-
Carlos E. R.
-
Michael Satterwhite