> The attached patch do not really fix this, but can be used as a basis. > > I think we all agree that the user must be warned, don't we?
Sure > > The problem is shall we remove the group or not? Do we need a special > return value? We shouldn't remove the group because this would induce inconsistencies in users databases. > What should the warning tell? Currently: > Warning: The primary group of bug295416 (bug295416, GID=1003) > will be removed, but is also the primary group of other295416 > (ID=1002). "Cannot remove group %s which is a primary group for another user" And a dedicated exit code (not sure about this as this could break some utilities relying on non zero exit code to check that the user has indeed been removed) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
