I believe I have found the answer. Further examination of the old syslogd init script showed that at the daemon's startup the chroot log devices were being linked to the device in /home/virtual/FILESYSTEMTEMPLATE. This step is obviously not taking place now. Thanks again for all of your help. On 04May2007 04:12PM (-0400), Centyx Centalix wrote:
/home/virtual/FILESYSTEMTEMPLATE/log- is used inside of many chroots, but is created as a hardlink in the chrooted environments, so I wouldn't think that this would be an issue. However, it would make sense that the local delivery logs were missing if syslog-ng were having problems w/ the log device that was used by the chroot. How may I go about troubleshooting that the log device is functioning properly and being read by syslog-ng?
Thanks for all of your input!
_______________________________________________ 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
-- If we don't try, we don't do. And if we don't do, why are we here...?