cmkelley
Very Senior Member
(asking here for a wider audience than might see it in the scribe thread)
To those who are familiar with the firmware source:
Other than at boot, when I clearly can kill them when S01syslog-ng starts, what actions might restart syslogd and/or klogd? I honestly have no idea of what I'd search for to try to figure this out myself. If it's something that would kick off one of the other scripts anyways, I can add a check and kill there rather than adding a cron job.
Just killing syslogd at boot has appeared to work okay, but @Cam reported that something restarted klogd, although he's not sure what.
To those who are familiar with the firmware source:
Other than at boot, when I clearly can kill them when S01syslog-ng starts, what actions might restart syslogd and/or klogd? I honestly have no idea of what I'd search for to try to figure this out myself. If it's something that would kick off one of the other scripts anyways, I can add a check and kill there rather than adding a cron job.
Just killing syslogd at boot has appeared to work okay, but @Cam reported that something restarted klogd, although he's not sure what.
Last edited: