Project

General

Profile

Bug #7013

Changing group scope to remote does not remove it from group file

Added by Kill Bill almost 2 years ago. Updated 4 months ago.

Status:
Resolved
Priority:
Low
Category:
User manager
Target version:
Start date:
12/15/2016
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.3.x
Affected Architecture:
All

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.

Associated revisions

Revision 64fa4207 (diff)
Added by Steve Beaver 4 months ago

Fixed #7013
Added warning requiring reboot if group scope is changed

History

#1 Updated by Kill Bill almost 2 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.

#2 Updated by Jim Thompson almost 2 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.

#3 Updated by Renato Botelho about 1 year ago

  • Target version changed from 2.4.0 to 2.4.1

#4 Updated by Jim Pingle about 1 year ago

  • Target version changed from 2.4.1 to 2.4.2

#5 Updated by Jim Thompson 12 months ago

  • Assignee set to Renato Botelho

#6 Updated by Renato Botelho 11 months ago

  • Target version changed from 2.4.2 to 2.4.3

#7 Updated by Jim Pingle 8 months ago

  • Target version changed from 2.4.3 to 2.4.4

#8 Updated by Steve Beaver 4 months 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.

#9 Updated by Steve Beaver 4 months ago

  • % Done changed from 0 to 100

#10 Updated by James Dekker 4 months 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

#11 Updated by Renato Botelho 4 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF