Problems writing to a file if destination is not /var/log
Hi, Before I used Suse 10.0 ( syslog-ng-1.6.8-3.2) , the router logfiles were send to another directoy /log/syslog. Via php-syslog-ng, the messages were also send via a pipe to a MySql database. -> no problems. Now I setup a new server withe Suse 10.2 (syslog-ng-1.6.11-23) but the logfiles outsite /var/log are not working: I get a Permission denied message, also no permission to write to the /var/log/pipe connection (php-ssylog-ng). When I send the log messages to another directory/file in /var/log than it works. How can I solve the permission problem? Rem: A chmod like 777 don't help, its like the daemons checks if the directory /var/log used + pipes or links are not allowed!
Hi,
Before I used Suse 10.0 ( syslog-ng-1.6.8-3.2) , the router logfiles were send to another directoy /log/syslog. Via php-syslog-ng, the messages were also send via a pipe to a MySql database. -> no problems.
Now I setup a new server withe Suse 10.2 (syslog-ng-1.6.11-23) but the logfiles outsite /var/log are not working: I get a Permission denied message, also no permission to write to the /var/log/pipe connection (php-ssylog-ng). When I send the log messages to another directory/file in /var/log than it works.
How can I solve the permission problem?
Rem:
A chmod like 777 don't help, its like the daemons checks if the directory /var/log used + pipes or links are not allowed!
Are you using AppArmor, aren't you? Try disabling AppArmor first and when syslog-ng works then review/update your AppArmor conf. 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.
participants (2)
-
Geller, Sandor (IT)
-
Luc Evers