Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
this is a first implementation of the systemd unit for chilli.service, although there are a few issues.
I wanted to build something more systemd-oriented than just a wrapper around the sysVinit script. Here some of the problems:
/var/run/chilli.$HS_LANIF.pid
is impossible mainly due to this systemd issue so I had to move to just/run/chilli.pid
(also, systemd reports use of/var/run
is deprecated an on my setup is in fact a symlink to/run
). In my understanding, the current init script don't provide any support for multiple interfaces but, if needed, we could use thechilli@interface
syntax of systemd to trick the situation.chilli
runs aschilli
user but needs to be invoked by root, so that it writes the.cfg.bin
file. The most meaningful solution would be either to write the.cfg.bin
file withExecStartPre
or to move the file to a location (e.g./var/spool/chilli
) writable by the chilli user. Is one of this possible?refs #540