Hello,
thank you for your answers!
Martin Pitt wrote:
> nusenu [2016-08-17 16:02 +]:
>> according to the official documentation from upstream systemd [1] it is
>> possible to override a package generator by placing a custom generator
>> (with the same name) into /etc/sy
simply to old for this feature?
When has it been introduced?
Is there another workaround that one could apply?
thanks,
nusenu
[1] https://www.freedesktop.org/software/systemd/man/systemd.generator.html
background:
https://github.com/nusenu/ansible-relayor/issues/72
https://lists.torproject.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Lennart Poettering:
> On Mon, 18.05.15 18:31, nusenu (nus...@openmailbox.org) wrote:
>
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>>
>>>>>>> I'm running into a problem with systemd&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>> I'm running into a problem with systemd's hardening features
>> ReadOnlyDirectories and ReadWriteDirectories *when* using them
>> in multi-instance service files - temp. workaround was to disable
>> them [1].
>>
>> - - that the service works fin
ACE
I found a similar problem in the systemd's bugtracker, and added a
comment there [2], but since this is a RFE and I'm looking more at a
bug, it might has been a bad idea to use the existing bug entry
instead of opening a new one?
Should I open a distinct bugzilla entry for this?
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>> I'm currently preparing a systemd service file for tor [1].
>>
>> We make use of CapabilityBoundingSet and first we had it set to:
>>
>> CapabilityBoundingSet = CAP_SETUID CAP_SETGID
>> CAP_NET_BIND_SERVICE
>>
>> but after noticing that reloads
> thanks for your reply.
>
>> systemctl should still support it if your system supports
>> chkconfig to manage initscripts.
>
> chkconfig was indeed not installed, but even after installing it,
> the is-enabled command output and return codes do not change:
>
>>> Output in such cases:
>>
>>> "F
n such cases:
>
>> "Failed to get unit file state for FOO.service: No such file or director
>> y"
Is this considered a bug?
thanks,
Nusenu
testing on:
Debian 8 (chkconfig installed) with systemd 215-14 and
Ubuntu 15.04 with systemd
iki/Software/systemd/Incompatibilities/
but I didn't find an answer to my question.
thanks,
Nusenu
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJVKtz2AAoJEFv7XvVCELh0VhIP/RaV7gf779K4dzWUYJHA29ks
d14KxPa7JPgn9RKfbq+wi1ZE84v+l5g6Gy5lR+3dMwJC8lj2mJxSlRYyynhIpCnf
dHpwMAdAMZxgXp
no longer be able to kill
> processes
thanks for the links. so you are saying this is just a bug and indeed
not expected?
thanks,
Nusenu
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJVCwGpAAoJEFv7XvVCELh0DDUP/3RF5qsT44IWEunRwnuEQELc
rnGV4LcBMf+q09r5bYTN/HG1djaKlhePgUgP3QNL
every
service requires CAP_KILL for proper reloads with systemctl?
Is it possible to specify distinct CapabilityBoundingSets for the
service (ExecStart) and the reload (ExecReload)?
thanks,
Nusenu
I'm testing on debian jessie (using systemd 215).
[1]
https://github.com/nusenu/tor-mult
11 matches
Mail list logo
