Currently, ccs implements overwriting semantics when setting properties
of some cluster configuration items.  Unfortunately, structure of Cluster
Administration guide may make users think the opposite as in section
5.5. Configuring Fence Devices, it contains these two separate
instructions:

To configure a value for the post_fail_delay attribute, execute
the following command:
> ccs -h host --setfencedaemon post_fail_delay=value

To configure a value for the post_join attribute, execute
the following command:
> ccs -h host --setfencedaemon post_join_delay=value

This operates with false assumption the semantics of set-commands is
additive.  If it would be true, the separation would be perfectly OK.
However, it is not;  running these two commands in sequence means
that with the second command, you will cancel the effect of the first
one (post_fail_delay property is dropped upon setting post_join_delay).

To unbend this, there should be no occurrence of configuring one item
(such as fence daemon) in more steps, i.e., everything set at once.

E.g.,:
> ccs -h host --setfencedaemon post_fail_delay=value post_join_delay=value

Additionally, there should probably be a warning box at the beginning
of the section explaining the implemented semantics and the danger
of loosing already configured properties with subsequent configuration
steps.

Adding Chris as he is the right person to discuss this with.