[Pkg-haproxy-maintainers] Syslog via /dev/log

[Apollon Oikonomopoulos]

Hi,

I just pushed a set of changes to use /dev/log for logging by default. IMHO,
#649085[1] has a point and we can now support logging out of the box in a
pristine Debian installation. So, apart from general thoughts and comments
(which are always welcome), I'd like your opinion on the following 
subjects:

1. Should postinst attempt to restart rsyslog or not, in order to create
   /dev/log in the chroot?  My gut feeling says "no" for a number of reasons
   (at least not without prompting) and my feeling is that the correct
   behaviour would be for the rsyslog package to register a trigger for
   /etc/rsyslog.d/*.

2. Should we document manual measures for more syslog implementations 
   (e.g. syslog-ng, dsyslog, ...)?

Cheers,
Apollon

[1] http://bugs.debian.org/649085

---

Apollon Oikonomopoulos (7):
      Add support for logging via /dev/log in chroot
      Rename debian/NEWS.Debian to debian/NEWS
      Log via /dev/log by default, document in NEWS.Debian
      Document enabling chroot by default
      Thoroughly document /dev/log logging in debian/README
      Changelog entry for syslog changes
      Use a persistent chroot dir (/var/lib/haproxy)