Bug#761403: CAP_KILL

2015-05-09 Thread Arto Jantunen
Attached is a patch that creates a separate service file under debian/ as requested. -- Arto Jantunen >From 1e30ccab0b0f486601021789248cf346517a0adc Mon Sep 17 00:00:00 2001 From: Arto Jantunen Date: Fri, 8 May 2015 13:03:00 +0300 Subject: [PATCH] Add systemd service file Add a new systemd ser

Bug#761403: CAP_KILL

2015-05-06 Thread Arto Jantunen
Peter Palfrader writes: > On Wed, 06 May 2015, Arto Jantunen wrote: >> I was planning to move to Type=notify + User=debian-tor + >> RuntimeDirectory=/var/run/tor in the service file, and a separate >> config instead of the current tor-service-defaults-torrc (without >> PidFile, RunAsDaemon and Us

Bug#761403: CAP_KILL

2015-05-06 Thread Peter Palfrader
On Wed, 06 May 2015, Arto Jantunen wrote: > Peter Palfrader writes: > > > On Wed, 06 May 2015, Arto Jantunen wrote: > > > >> ++Type = forking > > > > I'm not sure why we'd continue to detach when running under systemd. > > My plan was to do this in stages, starting with a service file that > wo

Bug#761403: CAP_KILL

2015-05-06 Thread Arto Jantunen
Peter Palfrader writes: > On Wed, 06 May 2015, Arto Jantunen wrote: > >> ++Type = forking > > I'm not sure why we'd continue to detach when running under systemd. My plan was to do this in stages, starting with a service file that works the same way as the current init script, working with the s

Bug#761403: CAP_KILL

2015-05-05 Thread Peter Palfrader
On Wed, 06 May 2015, Arto Jantunen wrote: > ++Type = forking I'm not sure why we'd continue to detach when running under systemd. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating S

Bug#761403: CAP_KILL

2015-05-05 Thread Arto Jantunen
nusenu writes: Actually also CAP_KILL is needed, otherwise reload will not work. >>> > >>> > CAP_KILL is not needed, see: >>> > https://lists.torproject.org/pipermail/tor-dev/2015-April/008759.html >> Well. You can either do that, or add CAP_KILL. Either will work you >> chose one and I chos

Bug#761403: CAP_KILL

2015-05-05 Thread nusenu
>>> Actually also CAP_KILL is needed, otherwise reload will not work. >> > >> > CAP_KILL is not needed, see: >> > https://lists.torproject.org/pipermail/tor-dev/2015-April/008759.html > Well. You can either do that, or add CAP_KILL. Either will work you > chose one and I chose the other. With the

Bug#761403: CAP_KILL

2015-05-05 Thread Arto Jantunen
nusenu writes: > Arto Jantunen: >> Actually also CAP_KILL is needed, otherwise reload will not work. > > CAP_KILL is not needed, see: > https://lists.torproject.org/pipermail/tor-dev/2015-April/008759.html Well. You can either do that, or add CAP_KILL. Either will work, you chose one and I chose

Bug#761403: CAP_KILL

2015-05-05 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Arto Jantunen: > Actually also CAP_KILL is needed, otherwise reload will not work. CAP_KILL is not needed, see: https://lists.torproject.org/pipermail/tor-dev/2015-April/008759.html Feels a bit as if you are re-making my steps ;) It might make se

Bug#761403: CAP_KILL

2015-05-04 Thread Arto Jantunen
Actually also CAP_KILL is needed, otherwise reload will not work. -- Arto Jantunen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org