ZNC can modify its own config file (znc.conf) during runtime, for
example using controlpanel or webadmin modules. Manually editing the
znc.conf file while znc is running is strongly discouraged.
Thus prodc should not watch this file, it would just lead to znc being
restarted unnecessarily.
As it happens, no restarts were done, because the watched path was
specified incorrectly. It used ZNC_CONFIG instead of ZNC_CONFIG_DIR,
and so it watched /tmp/etc/znc/configs/znc.conf/configs/znc.conf which
does not exist.
Remove the watch of znc.conf as it is not needed.
Signed-off-by: Ralph Siemsen <ralph.siemsen@linaro.org>
Create & run znc as a specific user rather than nobody. Converted to
use procd, removing dependencies on znc's 'droproot' module & 'su'
Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
ZNC 1.6.0 now verifies SSL certificates on connect, and some Servers
do not use a valid one (e.g. freenode).
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
