Re: init system policy

2014-11-18 Thread Eric Valette
On 18/11/2014 17:39, Matthias Urlichs wrote: Text emails, please. I alway forget that in my company my mailer is configured for html as outlook discussion cut is absurd... You _can_ do ExecStart=sudo -u $USER_MINIDLNA -g GROUP_MINIDLNA /usr/sbin/minidlnad -S but that's not the o

Re: init system policy

2014-11-18 Thread Matthias Urlichs
Hi, [ redirecting to debian-devel, as -policy isn't the correct list for this IMHO ] Eric Valette: > Text emails, please. > I've been fighting with some script conversion to systemd and I think > a reasonnably complex exemple should be of great help. I've been What's "reasonably compl

Re: Re: init system policy

2014-11-18 Thread Eric Valette
I've been fighting with some script conversion to systemd and I think a reasonnably complex exemple should be of great help. I've been trying to convert minidlna sysv init file to systemd, managed to have a working unit file but failed to split the configuration mimicing

Re: init system policy

2014-11-17 Thread Simon McVittie
On 17/11/14 19:20, Anthony Towns wrote: > Where possible, units should not use Type=forking or PIDFile, > but instead should invoke daemons with options > that tell them to remain in the foreground. This allows > systemd to provide better monitoring of the process. I understand what you're trying

Re: init system policy

2014-11-17 Thread Anthony Towns
On 16 November 2014 23:28, Anthony Towns wrote: > Hi *, > > I've drafted up a document that I think matches reality on how init > systems work in Debian. It's at: > > https://github.com/ajtowns/debian-init-policy > > and in (hopefully) easy-to-read pdf format at: > > > https://github.com/ajtown

init system policy

2014-11-16 Thread Anthony Towns
Hi *, I've drafted up a document that I think matches reality on how init systems work in Debian. It's at: https://github.com/ajtowns/debian-init-policy and in (hopefully) easy-to-read pdf format at: https://github.com/ajtowns/debian-init-policy/releases/download/2014-11-16-1/init-policy.pdf