From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fcrontab - what am I missing [SOLVED]
Date: Fri, 23 Oct 2009 18:55:32 +0200 [thread overview]
Message-ID: <200910231855.32211.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <tkrat.36220133aa91ef01@igpm.rwth-aachen.de>
On Friday 23 October 2009 17:51:19 Helmut Jarausch wrote:
> Hi,
>
> after hunting around for some weeks now, I've finally found the culprit
> to my permission problems with fcron[tab]
>
> First,
> some Gentoo package must have changed the UID of several executables
> and directories of the sys-process/fcron package to 'stunnel'
> instead of 'fcron'.
> I've found and fixed these long ago but still it didn't work.
> Now, I've found out, that in
> /etc/passwd
> the user 'fcron' had a GID which wasn't in /etc/group any longer.
> Probably, when sys-process/fcron is reinstalled, portage does not
> seem to change the entry in /etc/passwd (which it has created
> itself some time ago)
Without looking through the ebuilds, I'd guess the ebuild runs
useradd -r <daemon_name>
which will always lead to your problem sooner or later.
IMNSHO, /etc/{passwd,shadow,group} really should be part of the base install
with all daemon users pre-defined. Use the range 1-99 for this, it will take a
very long time to accumulate more than 99 daemon UIDs and one can confidently
know what UID a given system user required by an ebuild ought to be.
The implementation is obviously more complex than dropping a file on the file
system, so a simple API is required. Nonetheless, the idea is still sound.
The alternate is to expect users to know to run
find / -nouser -o -nogroup
at the magic points where it will be useful. Which is ludicrous.
--
alan dot mckinnon at gmail dot com
prev parent reply other threads:[~2009-10-23 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 15:51 [gentoo-user] fcrontab - what am I missing [SOLVED] Helmut Jarausch
2009-10-23 16:55 ` Alan McKinnon [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=200910231855.32211.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@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