On 12/04/2015 10:59 AM, Jan Pokorný wrote: > Btw. was any other architectural approach considered? It's sad > that multiplatform IPC, which is what might be better to handle > more or less continuous one-way stream of updates (would the exec > mechanism apply some kind of rate-limiting to prevent exhaustion?), > but what about
There is no rate limiting on the Pacemaker end. If there winds up being a big demand for it, we can look into it, but that is more likely to be useful within the script itself (a script that notifies another service of status changes likely does not want rate limiting, but an SMS notifier sure might). > long-lived unix sockets or named pipes? Especially the latter > might be doable in the agent just in shell + coreutils and other > basic tooling and might play well with file discovery approach. Simple shell scripts are often the limit of sysadmins' abilities in this area, so the less they have to know/do the better. _______________________________________________ Developers mailing list Developers@clusterlabs.org http://clusterlabs.org/mailman/listinfo/developers