#29 bad behaviour when doing cpu usermod

[Sven Linstaedt]

i am using CPU 1.4.3 on debian sarge and i dont know
wether this is intentionally or a bug:
when i do a "cpu usermod" all of my secondary group
memberships are resetted.
when specifiing the -G option with an empty list this
would be normal behaviour in my oppinion. but even if i
dont specify this option (e.g. i just want want to
change users passwd, gecos or something else), the
secondary group memberships are resetted to be empty.
as a workaround i had to look up the group memberships
before i modify a user in any way (doing a "cpu cat").
then i could do a "cpu usermod" giving the -G option
with the desired memberships and any other modifiing
option.

i cant imagine that behaviour is wanted :)

[Chris Wilson]

Logged In: YES
user_id=55851

I agree, I get this as well and I hate it.

If cpu bugs aren't being fixed (this one is a year old) is there a better
command-line tool for LDAP manipulation?

I would also like methods to add and remove users from individual
secondary groups, without having to give the whole list of groups
again (which takes a lot of time or a lot of black magick with sed).