Why did I need to *reboot* to change my group membership [duplicate]





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







5
















This question already has an answer here:




  • After adding a group, logout+login is not enough in 18.04?

    3 answers




Attempting to install MythTV on Ubuntu 18.04, I ran...



sudo usermod -a -G mythtv roger


...and logged out and back in. This should be sufficient. But: my group memberships didn't change.



I had to reboot. Why?










share|improve this question













marked as duplicate by user535733, Fabby, Eric Carvalho, qbi, pomsky May 14 at 5:21


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • Could very well be the cause in the linked dupe. systemd strikes again, I guess.

    – Roger Lipscombe
    May 12 at 21:54


















5
















This question already has an answer here:




  • After adding a group, logout+login is not enough in 18.04?

    3 answers




Attempting to install MythTV on Ubuntu 18.04, I ran...



sudo usermod -a -G mythtv roger


...and logged out and back in. This should be sufficient. But: my group memberships didn't change.



I had to reboot. Why?










share|improve this question













marked as duplicate by user535733, Fabby, Eric Carvalho, qbi, pomsky May 14 at 5:21


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.



















  • Could very well be the cause in the linked dupe. systemd strikes again, I guess.

    – Roger Lipscombe
    May 12 at 21:54














5












5








5









This question already has an answer here:




  • After adding a group, logout+login is not enough in 18.04?

    3 answers




Attempting to install MythTV on Ubuntu 18.04, I ran...



sudo usermod -a -G mythtv roger


...and logged out and back in. This should be sufficient. But: my group memberships didn't change.



I had to reboot. Why?










share|improve this question















This question already has an answer here:




  • After adding a group, logout+login is not enough in 18.04?

    3 answers




Attempting to install MythTV on Ubuntu 18.04, I ran...



sudo usermod -a -G mythtv roger


...and logged out and back in. This should be sufficient. But: my group memberships didn't change.



I had to reboot. Why?





This question already has an answer here:




  • After adding a group, logout+login is not enough in 18.04?

    3 answers








18.04 user-management groups






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 12 at 14:31









Roger LipscombeRoger Lipscombe

202111




202111




marked as duplicate by user535733, Fabby, Eric Carvalho, qbi, pomsky May 14 at 5:21


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.









marked as duplicate by user535733, Fabby, Eric Carvalho, qbi, pomsky May 14 at 5:21


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • Could very well be the cause in the linked dupe. systemd strikes again, I guess.

    – Roger Lipscombe
    May 12 at 21:54



















  • Could very well be the cause in the linked dupe. systemd strikes again, I guess.

    – Roger Lipscombe
    May 12 at 21:54

















Could very well be the cause in the linked dupe. systemd strikes again, I guess.

– Roger Lipscombe
May 12 at 21:54





Could very well be the cause in the linked dupe. systemd strikes again, I guess.

– Roger Lipscombe
May 12 at 21:54










1 Answer
1






active

oldest

votes


















6














Likely because /etc/gshadow was not updated (but don't ask me why that didn't happen as usermod should do that too; check /var/log/ if there is a notice). The 2 files important for groups are /etc/group and /etc/gshadow where gshadow supersedes group.



When both are correct logging out and in is enough to update the group for the user. If only the 1st was updated you will need to reboot or you can update gshadow with the grpconv command. Logging out and in is then enough.






share|improve this answer



















  • 4





    Why does reboot fix it then?

    – Joshua
    May 12 at 19:11






  • 1





    A bug in systemd where they created a fix during boot

    – Rinzwind
    May 13 at 6:13


















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









6














Likely because /etc/gshadow was not updated (but don't ask me why that didn't happen as usermod should do that too; check /var/log/ if there is a notice). The 2 files important for groups are /etc/group and /etc/gshadow where gshadow supersedes group.



When both are correct logging out and in is enough to update the group for the user. If only the 1st was updated you will need to reboot or you can update gshadow with the grpconv command. Logging out and in is then enough.






share|improve this answer



















  • 4





    Why does reboot fix it then?

    – Joshua
    May 12 at 19:11






  • 1





    A bug in systemd where they created a fix during boot

    – Rinzwind
    May 13 at 6:13
















6














Likely because /etc/gshadow was not updated (but don't ask me why that didn't happen as usermod should do that too; check /var/log/ if there is a notice). The 2 files important for groups are /etc/group and /etc/gshadow where gshadow supersedes group.



When both are correct logging out and in is enough to update the group for the user. If only the 1st was updated you will need to reboot or you can update gshadow with the grpconv command. Logging out and in is then enough.






share|improve this answer



















  • 4





    Why does reboot fix it then?

    – Joshua
    May 12 at 19:11






  • 1





    A bug in systemd where they created a fix during boot

    – Rinzwind
    May 13 at 6:13














6












6








6







Likely because /etc/gshadow was not updated (but don't ask me why that didn't happen as usermod should do that too; check /var/log/ if there is a notice). The 2 files important for groups are /etc/group and /etc/gshadow where gshadow supersedes group.



When both are correct logging out and in is enough to update the group for the user. If only the 1st was updated you will need to reboot or you can update gshadow with the grpconv command. Logging out and in is then enough.






share|improve this answer













Likely because /etc/gshadow was not updated (but don't ask me why that didn't happen as usermod should do that too; check /var/log/ if there is a notice). The 2 files important for groups are /etc/group and /etc/gshadow where gshadow supersedes group.



When both are correct logging out and in is enough to update the group for the user. If only the 1st was updated you will need to reboot or you can update gshadow with the grpconv command. Logging out and in is then enough.







share|improve this answer












share|improve this answer



share|improve this answer










answered May 12 at 14:45









RinzwindRinzwind

214k28413552




214k28413552








  • 4





    Why does reboot fix it then?

    – Joshua
    May 12 at 19:11






  • 1





    A bug in systemd where they created a fix during boot

    – Rinzwind
    May 13 at 6:13














  • 4





    Why does reboot fix it then?

    – Joshua
    May 12 at 19:11






  • 1





    A bug in systemd where they created a fix during boot

    – Rinzwind
    May 13 at 6:13








4




4





Why does reboot fix it then?

– Joshua
May 12 at 19:11





Why does reboot fix it then?

– Joshua
May 12 at 19:11




1




1





A bug in systemd where they created a fix during boot

– Rinzwind
May 13 at 6:13





A bug in systemd where they created a fix during boot

– Rinzwind
May 13 at 6:13



Popular posts from this blog

He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

Bunad

Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum