Turns out not to be a 384.11 problem only ...
I had been counting on syslogd and klogd only being restarted via the "restart logger" service event. However, I have found that they also restart after a "restart time" service event.
This is further complicated by the fact that a "restart time"...
