Public bug reported:
as seen in bug #2133460, specifically
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/2133460/comments/7:
haproxy is currently run in a chroot that gets a dedicated logging socket from
rsyslogd.
we should consider dropping this approach, instead logging directly with
journald.
additionaly, we could get rid of the chroot, and instead use systemd's
confinement offerings.
** Affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2136303
Title:
use systemd confinements and journal logging instead of rsyslog +
chroot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/2136303/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
