Geller, Sandor (IT) wrote:
Hi,

  
Hi,

I am using openSUSE 10.3 with syslog-ng 1.6.12-33 with the following
configuration file:

#
source s_file { internal(); };
destination d_file { file("/home/uga/Daten/system/system.msg"); };
log { source(s_file); destination(d_file); };

You see, it's really simple. ls -l displays for the file:

-rw-rw-rw- 1 root root     0 2008-02-07 22:03 system.msg

So system.msg is writable for all. But nothing is logged to the file,
even after restart. The FAQ mentions a similar case
(http://www.campin.net/syslog-ng/faq.html#dupe_sources) but 
the problem
here are clearly duplicate  sources in the directives. This is not the
case here. Any ideas are very welcome.
    

Seeing your mails about problems on openSuse rings a bell: AppArmor. Are
you sure it doesn't block syslog-ng on your system?

regards,

Sandor
--------------------------------------------------------

NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
_______________________________________________
syslog-ng maillist  -  syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng
Frequently asked questions at http://www.campin.net/syslog-ng/faq.html


  
Your bell is pretty good. AppAmour was in fact the problem. I dind't expect that Novell would block a component of its own OS. Thank you very much.

Best regards,
Uwe