Ken Gaillot <kgail...@redhat.com> writes:

> libqb would simply provide the API for reopening the log, and clients
> such as pacemaker would intercept the signal and call the API.

Just for posterity: you needn't restrict yourself to signals.  Logrotate
has nothing to do with signals.  Signals are a rather limited form of
IPC, which might be a good tool for some applications.  Both Pacemaker
and Corosync already employ much richer IPC mechanisms, which might be
more natural to extend for triggering log rotation than adding a new IPC
mechanism.  Logrotate optionally runs scripts before and after renaming
the log files; these can invoke kill, corosync-cmapctl, cibadmin and so
on all the same.  It's entirely your call.
-- 
Regards,
Feri
_______________________________________________
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to