Jumpstarter
Senior Member
so if scripts are using logger could that be causing the issue?I'm not sure I understand your meaning. All of the logs created by syslog-ng are put in the /opt/var/log directory. All of the information comes from the system logging utility, except for 2 files generated by logrotate that syslog-ng reads and puts together into one log file in /opt/var/log. None of the syslog-ng files should be triggering syslogd.
I've tried to get syslogd running and I couldn't. Everything I've tried to start syslogd outside of restarting the logger or time functions has failed to start it. When I use the logger or time functions they are properly captured by service-event and killed off.
Did you edit your service-event file with a windows editor? That would stop service-event from working.
BTW --- this is all that is in service-event script
is what the ps | grep log shows
and this is also listed inside the debug file generated.
Last edited: