Building out a new syslog-ng server and it seems that in syslog-ng 3.0.5 is chrooting before reading the config file and setting up /dev/log. I ran the same configuration in syslog 2.0.7 without this problem. /opt/syslog-ng/sbin/syslog-ng --chroot /var/log Error opening configuration file; filename='/opt/syslog-ng/etc/syslog-ng.conf', error='No such file or directory (2)' --- Larry Low
On Thu, 2009-12-10 at 14:16 -0800, Larry Low wrote:
Building out a new syslog-ng server and it seems that in syslog-ng 3.0.5 is chrooting before reading the config file and setting up /dev/log. I ran the same configuration in syslog 2.0.7 without this problem.
/opt/syslog-ng/sbin/syslog-ng --chroot /var/log Error opening configuration file; filename='/opt/syslog-ng/etc/syslog-ng.conf', error='No such file or directory (2)'
That's right, this was changed in 3.0 because with the earlier method, you couldn't reload syslog-ng, you always had to use restart. -- Bazsi
On Thu, 2009-12-10 at 14:16 -0800, Larry Low wrote:
Building out a new syslog-ng server and it seems that in syslog-ng 3.0.5 is chrooting before reading the config file and setting up /dev/log. I ran the same configuration in syslog 2.0.7 without this problem.
/opt/syslog-ng/sbin/syslog-ng --chroot /var/log Error opening configuration file; filename='/opt/syslog- ng/etc/syslog-ng.conf', error='No such file or directory (2)'
That's right, this was changed in 3.0 because with the earlier method, you couldn't reload syslog-ng, you always had to use restart.
Documentation should be updated to reflect this. It reflects pre-3.0 as far as reloading is concerned. I know personally I would rather have to restart syslog-ng during a change than having to restructure to have syslog-ng chrooted.
-- Bazsi
participants (2)
-
Balazs Scheidler
-
Larry Low