Package: unbound
Version: 1.9.0-2
Update to upstream release 1.9.1 to address some issues in OOOR,
QNAME minimization and more.
upstream announcement and changelog:
https://nlnetlabs.nl/pipermail/unbound-users/2019-March/011415.html
Thanks for implementing this!
There are two typos in tor-instance-create.8.txt:
18,19c18,19
< daemon. This can be useful if you want to run multiple relays or brdige
< relays on a single system, of if you want to provide a hidden service in
---
> daemon. This can be useful if you want to run
Package: tor
Severity: wishlist
For users or relay operators that run multiple tor instances on a
single host a multi-instance systemd service file is handy.
I'm using a similar systemd unit file in my ansible-relayor configuration:
https://github.com/nusenu/ansible-relayor/blob/master/templates
Do you maybe have anything installed on your upgraded system which might
interfere with systemd, like cgmanager, lxc, cgroup-bin etc.
upgraded-system# dpkg -l cgmanager lxc cgroup-bin
dpkg-query: no packages found matching cgmanager
dpkg-query: no packages found matching lxc
dpkg-query: no
Can you find out what is different between the upgraded and fresh Debian
installation?
systemd version is on both (fresh and upgraded) systems 215-17, what
else should I check?
Can you post the complete service file you are using, please?
working service file
(to make it fail on upgraded
systemd version is on both (fresh and upgraded) systems 215-17, what
else should I check?
Eg. diff the list if installed packages you get via dpkg
--get-selections and look for suspicouos diffs.
The upgraded system has sysvinit installed, the fresh one doesn't.
Both have systemd-sysv.
/nusenu/ansible-relayor/commit/4f6283e6d993e6f81a632007c823797253feee38
Note in upstream bugtracker:
https://bugs.freedesktop.org/show_bug.cgi?id=89875#c2
[2]
http://lists.freedesktop.org/archives/systemd-devel/2015-April/031377.html
http://lists.freedesktop.org/archives/systemd-devel/2015-May/031993
-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
entry.
and maybe also the closed issues in the tracker:
https://github.com/nusenu/ansible-relayor/issues?utf8=%E2%9C%93q=is%3Aissue+is%3Aclosed+systemd
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
not succeed).
I was able to use ControlSocket without CAP_FOWNER.
Adding CAP_DAC_OVERRIDE and CAP_CHOWN was enough in my case.
See also:
https://lists.torproject.org/pipermail/tor-dev/2015-April/008638.html
What tor version did you test with?
thanks,
nusenu
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Arto Jantunen:
With 0.2.6.7. Did you test both cases where /var/run/tor exists
and doesn't exist?
If /var/run/tor doesn't exist
+
ControlSocket /var/run/tor/control
in torrc
tor does not start with and without CAP_FOWNER:
[warn] Before Tor can
Hi,
please consider multi-instance support when adding a systemd service
file for tor.
For an example see:
https://github.com/nusenu/ansible-relayor/blob/master/templates/debian_tor%40.service
(this is a template file - simply remove lines 31,36-38)
CapabilityBoundingSet:
Since you add
/chkconfig tor --level=5
enabled
echo $?
0
references:
http://lists.freedesktop.org/archives/systemd-devel/2015-April/030652.html
http://lists.freedesktop.org/archives/systemd-devel/2015-April/030671.html
https://github.com/nusenu/ansible-relayor/issues/20
--
To UNSUBSCRIBE, email to debian-bugs-dist
duplicate
Sorry I just saw:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751638
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Control: affects -1 ansible
I am also annoyed by this bug because this makes Puppet thinks
that the service is not enabled as it should.
same with ansible
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
CapabilityBoundingSet = cap2
but that is not the case.
Merging multiple lines manually fixed the issue for me:
https://github.com/nusenu/ansible-relayor/commit/48df0a4738654ff6b0897493cf2811961550a7d6
https://github.com/nusenu/ansible-relayor/issues/19
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=89997
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
17 matches
Mail list logo
