From: Philipp Riegger <lists@anderedomain.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Managing users and groups
Date: Sun, 09 Sep 2007 10:15:52 +0200 [thread overview]
Message-ID: <1189325752.2950.3.camel@troy.riegger.name> (raw)
In-Reply-To: <46E37323.8000302@googlemail.com>
On Sun, 2007-09-09 at 06:14 +0200, Daniel Pielmeier wrote:
> A group/user is created when no other ebuild has the dependency and is
> removed when the last ebuild has been removed which needs it?
This blows up if you have to uninstall and reinstall a package, caused
by blockers or whatever. Files exist that still belong to the
user/group, new user/group have different ids. So either make sure the
uids and gids stay the same or just leave them be. Usually you have an
extra user for security reasons with minimal access rights. There is
absolutely no harm in that. I would prefer this to be another eclean
function or something like that, which scans passwd, shadow, group,
package database and all the files and dirs for owners.
Philipp
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-09-09 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 2:47 [gentoo-dev] Managing users and groups Daniel Pielmeier
2007-09-09 3:39 ` Mike Frysinger
2007-09-09 4:14 ` Daniel Pielmeier
2007-09-09 8:15 ` Philipp Riegger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1189325752.2950.3.camel@troy.riegger.name \
--to=lists@anderedomain.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox