And here is the solution (a colleague figured it out):
AppArmour needs to be told to allow access for syslog-ng.
Either:
# /usr/sbin/complain /sbin/syslog-ng
or edit /etc/apparmor.d/sbin.syslog-ng,
to add a line
/chroot/dev/log w,
then:
# /etc/init.d/boot.apparmor restart
followed by
# /sbin/service/syslog restart
I never ever heard of AppArmor before..
Patrick Haller wrote:
> On Tue, May 12, 2009 at 11:21:59PM +0800, Mathias Koerber wrote:
>> That actually all works, so I am still baffled..
>
> Wow. Try a different version of syslog-ng? If you want to run syslog-ng,
> opening up the source and turning on full debugging looks to be the only
> way out.
>
>
> Patrick
_______________________________________________
Slugnet mailing list
[email protected]
http://wiki.lugs.org.sg/LugsMailingListFaq
http://www.lugs.org.sg/mailman/listinfo/slugnet
