Re: Re: init system policy

2014-11-21 Thread Jonathan de Boyne Pollard
Eric Valette: I just mentioned that naively combining User=$TOTO or ${TOTO} TOTO > being defined in an default/package file parsed by EnvironmentFile= > does not seem to work as documented in man pages (seen the very same > question being asked on various distro mailing list without > definitiv

Re: Re: Re: init system policy

2014-11-21 Thread Jonathan de Boyne Pollard
Eric Valette: There has been a good and valuable effort trying to split original > upstream packages provided init system scripts by debian developers > into /etc/default/X and /etc/init.d/X file and storing most commonly > changed sysv init options in the default file part (including start > o

Re: Re: init system policy

2014-11-21 Thread Jonathan de Boyne Pollard
Russ Allbery: Yeah, this seems like the right solution to me too. Drop a > configuration fragment in /etc/systemd that overrides the user and > group and then don't touch it again. I refer you to footnote #85 in that patched document that I just sent to you. (-: -- To UNSUBSCRIBE, email

Re: Re: init system policy

2014-11-21 Thread Jonathan de Boyne Pollard
Vincent Bernat: There is chpst for this kind of task. Unfortunately, being part of > runit, it may not be suitable for a dependency. * http://superuser.com/a/72 Actually, there are chpst, s6-setuidgid, daemontools-encore setuidgid, daemontools setuidgid, freedt setuidgid, nosh setuidgid,

Re: Re: init system policy

2014-11-20 Thread David Weinehall
On Wed, Nov 19, 2014 at 02:51:57PM +, Ian Jackson wrote: > Laurent Bigonville writes ("Re: Re: init system policy"): > > Matthias Urlichs wrote: > > > See "man 5 sudoers" for details. > > > > You probably want to use "runuser"

Re: Re: init system policy

2014-11-20 Thread Eric Valette
> I did not know that. It is very interesting. > > But, is there a way to be notified at upgrade time that the > system service file has been modified when there is local > (partial or full) changes ? > As a small workaround, I think I will put symlinks such as > /lib/systemd/[perhaps sub-direc

Re: Re: init system policy

2014-11-19 Thread Ian Jackson
Laurent Bigonville writes ("Re: Re: init system policy"): > Matthias Urlichs wrote: > > See "man 5 sudoers" for details. > > You probably want to use "runuser" that has been introduced recently in > utils-linux Or `really' from chiark-really (

Re: Re: init system policy

2014-11-19 Thread Josselin Mouette
Eric Valette wrote: > well, debconf seems like a win here. > There's no reasonable default so it's desirable to make it easy for the > admin to specify and so you'd probably want to use normal best practice > for debconf updates. I agree with this but unf

Re: Re: init system policy

2014-11-19 Thread Laurent Bigonville
Matthias Urlichs wrote: > Hi, > > Steve Langasek: > > The disadvantage of the sudo method is that you are spawning a PAM > > session, which is not desirable for any service. > > > Ah. Thanks for the reminder; mentioning the session issue completely > slipped my mind. :-/ > > If one does need to

Re: Re: init system policy

2014-11-19 Thread Eric Valette
> well, debconf seems like a win here. > There's no reasonable default so it's desirable to make it easy for the > admin to specify and so you'd probably want to use normal best practice > for debconf updates. I agree with this but unfortunately original minidlna package as no debconf setup :-) --

Re: Re: init system policy

2014-11-18 Thread Eric Valette
Parsing User=$TOTO as "the User is the value of the environment variable TOTO as given by Environment or EnvironmentFile" might be a reasonable feature request, but it is not currently an implemented feature. I think anything that simplify transitioning from an init system to another new one is