[Pacemaker] Question about config

[Andrew Beekhof]

On Mon, May 7, 2012 at 7:52 PM, Kazunori INOUE
<inouekazu at intellilink.co.jp> wrote:
> Hi,
>
> On the Pacemkaer-1.1 + Corosync stack, is it specification not to read
> 'service' directive (use_logd option)?
> * https://github.com/ClusterLabs/pacemaker/blob/db5e16736cc2682fbf37f81cd47be7d17d5a2364/mcp/corosync.c#L520

Service blocks don't exist anymore in corosync 2.0, so that probably
explains the change.
Once the move to libqb logging and ipc is complete, support for logd
will likely go away - unless someone writes a logd target for libqb.

>
> Is it a future policy to set these options in /etc/sysconfig/pacemaker?
> as follows:
> ------------
> # For non-systemd based systems, prefix export to each enabled line
>
> # Enable this for compatibility with older corosync (prior to 2.0)
> # based clusters which used the nodes uname as its uuid also
> # PCMK_uname_is_uuid=no
>
> [snip]
> # VALGRIND_OPTS="--leak-check=full --trace-children=no --num-callers=25 --log-file=/tmp/pacemaker-%p.valgrind"
>
> export HA_LOGD=no
>
> ------------
>
> Since the default value of HA_LOGD may be "yes", we want to set "no".
> * http://hg.linux-ha.org/glue/file/66d5f0c135c9/lib/stonith/ha_log.sh#l31
>
> ----
> Best regards,
> Kazunori INOUE
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org