On Mon 2018-01-08 12:50:02 +0100, Jan Včelák wrote:
There is some confusion: Ubuntu 14.04 uses upstart,
15.04 is the first
version with systemd. I agree with Klaus that it would be reasonable
to build packages without systemd support for versions pre 15.04.
if the question is about where the logs go based on systemd, knot
compiled with systemd enabled will still work on machines that don't run
systemd. its logs will simply go directly to syslog, instead of using
sd_journal_send (see src/knot/common/log.c).
in particular, if knot is built with libsystemd, but is running on a
system that is not running systemd, use_journal will be false.
When knot sends log messages to syslog, whoever is listening on /dev/log
will get them. if you *are* running systemd locally, then that will be
systemd-journald. if syslog is *also* present on the system, then there
is usually some relay/hook for journald to pass inbound messages along
to the traditional syslog daemon.
If the local admin wants syslog to see the messages when journald is
listening on /dev/log, this is something for the local system
administrator to fix, and not something for knot to deal with. please
don't divert time/energy into building, distributing, and maintaining a
without-systemd package.
--dkg