On Mon, Oct 23, 2006 at 12:33:46PM +0200, Stefan Hornburg wrote:
> >>>drwxr-xr-x daemon/daemon 0 2006-09-09 21:54:23 ./var/run/courier/
> >>>drwxr-x--- daemon/daemon 0 2006-09-09 21:54:23
> >>>./var/run/courier/authdaemon/
> >>>* ask the maintainer or courier-authdaemon and courier-maildrop what's
> >>>their strategy with this whole daemon user thing :)
> >>
> >>The packages started with daemon years ago and I tried to allocate fixed
> >>UID/GID for courier, but that was denied. So I sticked with that. Any
> >>advice is welcome.
> >
> >Add a dynamic system user in maintainer scripts and use that? That way,
> >users of maildrop can switch to that when they have both programs
> >installed.
> >They'd still have to give up mail setgid, but for many people that's a
> >non-issue.
>
> This is a possible solution, yes. But certainly a post-etch thing.
Why? You think that many other users of authdaemon have already hardcoded
the daemon user?
It was like that in the previous stable release (sarge), so I don't see much
difference in whether we do it in etch or in etch+1, either way it's a
transition matter.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
