View previous topic :: View next topic |
Author |
Message |
justin025 n00b
Joined: 01 Jul 2024 Posts: 4
|
Posted: Sat Sep 07, 2024 8:30 pm Post subject: Why does portage lock acct-user ebuilds on unmerge |
|
|
I was just wondering why it makes more sense to lock an unused user instead of deleting it; for example qemu creates a user but after qemu is uninstalled the user is retained. Is there a specific reason why it was implemented this way and will I do any damage to my system by deleting extra accounts? |
|
Back to top |
|
|
dmpogo Advocate
Joined: 02 Sep 2004 Posts: 3425 Location: Canada
|
Posted: Sat Sep 07, 2024 9:51 pm Post subject: Re: Why does portage lock acct-user ebuilds on unmerge |
|
|
justin025 wrote: | I was just wondering why it makes more sense to lock an unused user instead of deleting it; for example qemu creates a user but after qemu is uninstalled the user is retained. Is there a specific reason why it was implemented this way and will I do any damage to my system by deleting extra accounts? |
Users are created by separate ebuilds, probably acct-user/gemu in your case which are dependency of the main package. To clear dependencies yiu need to run emerge --depclean, same as in the case dependency is some ljbrary |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22648
|
Posted: Sat Sep 07, 2024 9:53 pm Post subject: |
|
|
Removing a user account does not automatically remove all files owned by that account. If such files did exist, and the account were removed, a future user creation could accidentally assign that uid to some other name, with confusing or even security-sensitive consequences. By retaining the account, but locking it, future user creations are prevented from picking that uid unless explicitly forced to reuse an in-use uid. |
|
Back to top |
|
|
justin025 n00b
Joined: 01 Jul 2024 Posts: 4
|
Posted: Sat Sep 07, 2024 10:00 pm Post subject: |
|
|
Thanks for the explanation |
|
Back to top |
|
|
|