On 09/03/2013 02:43 AM, Christine
Caulfield wrote:
I've seen a few instances where corosync has shut down for apparently 'no reason'. In fact most of the time the shutdown has been caused by an external source (often an init script) but it's not been obvious what has happened and people implicate the deamon While the idea seems interesting, I would recommend generally not doing this in a signal handler, and figuring out another way to log the message. The logging code is not really designed to be called from a signal handler, and I expect even libqb has same problems. Angus could you add your insight on libqb signal handle logging? Regards -steve _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss |
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss