[Syslog-ng-maintainers] Bug#962839: syslog-ng-core: Conflicting help messages, bad control socket location

[Elliott Mitchell]

Package: syslog-ng-core
Version: 3.19.1-5
Severity: important

`man syslog-ng` =>

       --control <file>  or -c <file>
           Set the location of the syslog-ng control socket. Default value:
           /var/run/syslog-ng.ctl


`/usr/sbin/syslog-ng -h` =>

  -c, --control=<ctlpath>                                    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=<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+sigmsg at m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445