On 2/8/2010 10:49 PM, Steven Dake wrote: > On Mon, 2010-02-08 at 11:13 -0700, hj lee wrote: >> I noticed that this happens when corosync starts before syslog in init >> start order. I understand that corosync requires syslog, but at least >> it should start OK and should be operational OK even without syslog. >> > > thanks > > Would you file a defect indicating that corosync without a running > syslog doesn't operate properly? > > Regards > -steve
This is an interesting problem tho. All syslog calls are "void". There is no way to know if syslogd is running or not (unless we do some evil hacks). Are we entirely sure this isn´t a version specific bug of glibc/syslog? Fabio _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
