Bug #7013
closed
Changing group scope to remote does not remove it from group file
100%
Description
If I understand things correctly, after implementing Bug #6012 the groups with scope set to "Remote" are not supposed to be stored in /etc/group. However, when you edit an existing group and change the scope from "Local" to "Remote", it still stays in /etc/group.
Updated by Kill Bill about 8 years ago
Well, there's obviously much more wrong here, this actually requires a reboot to take effect. Also, adding/removing users to/from a group requires a reboot to take effect.
Updated by Jim Thompson almost 8 years ago
you would have to teach each affected process to re-run initgroups(3); setgroups(2); in order for them all to have a new group vector in their individual proc structures.
Updated by Renato Botelho over 7 years ago
- Target version changed from 2.4.0 to 2.4.1
Updated by Jim Pingle about 7 years ago
- Target version changed from 2.4.1 to 2.4.2
Updated by Renato Botelho about 7 years ago
- Target version changed from 2.4.2 to 2.4.3
Updated by Jim Pingle almost 7 years ago
- Target version changed from 2.4.3 to 2.4.4
Updated by Anonymous over 6 years ago
- Status changed from New to Feedback
Changing group scope from local to remote now deletes the group from /etc/group
Added a warning message to indicate that a reboot may be required for this to take effect.
Updated by Anonymous over 6 years ago
- % Done changed from 0 to 100
Applied in changeset 64fa4207182efea9b45f5170b8996b967441d4e1.
Updated by Anonymous over 6 years ago
On 2.4.4.a.20180705.0032 works as expected. After changing scope from Local to Remote, the group is removed from /etc/group
Updated by Renato Botelho over 6 years ago
- Status changed from Feedback to Resolved