dirmngr:#668890, #670700 Was: Re: systemd-fsck?
On Sun, 2014-05-11 at 18:48 +0200, Laurent Bigonville wrote:
> Marc Haber wrote:
> > On Sun, 11 May 2014 13:16:43 +0200, Martin Steigerwald
> > <Martin@lichtvoll.de> wrote:
> > >Am Sonntag, 11. Mai 2014, 12:53:39 schrieb Marc Haber:
> > >> On Sun, 11 May 2014 10:04:15 +0200, Cyril Brulebois
> > >> <kibi@debian.org>
> > >>
> > >> wrote:
> > >> >Marc Haber <mh+debian-devel@zugschlus.de> (2014-05-11):
> > >> >> Just curious as the maintainer of another package using su in
> > >> >> an init script since 2001, how am I supposed to start a
> > >> >> non-root process from an init script?
> > >> >
> > >> >start-stop-daemon has:
> > >> > -c, --chuid username|uid[:group|gid]
> > >>
> > >> Will a script doing this be portable to other Linuxes or even BSD
> > >> Unices?
> > >
> > >Good question and I think the answer is a no.
> > >
> > >So… instead of changing the script it may be better to provide a
> > >systemd unit file for dirmngr, then the script can remain as it is.
> >
> > This will also cause double effort since Debian needs special handling
> > that no other distribution obviously needs.
>
> Could you please explain me how it could cause double effort as the
> initscript the the dirmngr package is shipping is _already_ debian
> specific and that I don't see any initscript shipped by upstream in the
> tarball?
>
> The initscript had to be fixed anyway, I could indeed have also added a
> systemd sevice file but I didn't think it will fit a NMU.
Can we please separate the bugs in this thread: This one is about
dirnmgr not network-manager and gdm3 dragging in systemd as init
default, #747535.
Reply to: