Bug#962839: syslog-ng-core: Conflicting help messages, bad control socket location
Hi,
finally I was able to do some investigation related to this ticket.
The syslog-ng manpage need to be updated and I'll do that.
On the other hand, the ${localstatedir} and the ${exec_prefix} is more
like an upstream decision in how to handle things, than an actual bug.
For some reason, they decided to centralize the path handling into one
place (lib/reloc.c) and in every place they save the paths with the
variable and only expand the variables at use time. But for some
reason, the help screen is not counting as a use time and they did not
expand it.
Of course this can be also seen as a bug and for that reason I've
created a ticket in the upstream ticketing system to iron this out.
The upstream ticket is:
https://github.com/syslog-ng/syslog-ng/issues/4138
Bug#962839: syslog-ng-core: Conflicting help messages, bad control socket location
Package: syslog-ng-core
Version: 3.19.1-5
Severity: important
`man syslog-ng` =>
--control or -c
Set the location of the syslog-ng control socket. Default value:
/var/run/syslog-ng.ctl
`/usr/sbin/syslog-ng -h` =>
-c, --control=Set syslog-ng
control socket, default=${localstatedir}/syslog-ng.ctl
Then one observes AppArmor's audit log and discovers it is using
/var/lib/syslog-ng/syslog-ng.ctl instead. That "${localstatedir}" looks
suspiciously like an incorrect build.
There is another example of that in the help message:
--module-path= Set the list of
colon separated directories to search for modules,
default=${exec_prefix}/lib/syslog-ng/3.19
The syslog-ng-core package seems to have some trouble.
--
(\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/)
\BS (| ehem+sig...@m5p.com PGP 87145445 |) /
\_CS\ | _ -O #include O- _ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
