This also has an impact on any client applications which use SSSD for identity information the user with the conflict will not be found or accessible to those applications. For example, let’s say we wanted to change UserA’s GID from 1000 to 2000. This command takes two arguments: the name of the group you want to assign the user to and the username of the user you want to modify. If an existing user changes the UID number, that user is prevented from logging into SSSD and associated services and domains. To change the GID of a user, you will need to use the chgrp command. If you omit the -a option, the user will be removed from the groups not listed after the -G option. Always use the -a (append) option when adding a user to a new group. It interprets it as a different and new user, not an existing user with a different UID number. For example, to add the user linuxize to the games group, you would run the following command: sudo usermod -a -G games linuxize. What this means is that SSSD does not recognize UID number changes. If a user with the same name but a different UID attempts to log into the system, then SSSD treats it as two different users with a name collision. The UID number is then used as the identifying key for the user. If you do want to use sed, then something like sed /saned/s/\/home\/saned/\/bin/\/tcsh/' /etc/passwd should work. " When the user logs into a system or service, SSSD caches that user name with the associated UID/GID numbers. 1 usermod -m -d /bin/tcsh saned seems like a better approach.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |