diff options
| author | Martin Schwenke <martin@meltin.net> | 2014-07-02 11:08:45 +1000 |
|---|---|---|
| committer | Martin Schwenke <martin@meltin.net> | 2014-07-02 20:26:52 +1000 |
| commit | 55d315b1118283c60edaf365ef9b123eaea27bed (patch) | |
| tree | ea94c380ae841f32dea2505f05d296f89f5c8e31 /README | |
| parent | fa26aa2e805ff739f3969892e7e302daa1eaef60 (diff) | |
| download | autocluster-55d315b1118283c60edaf365ef9b123eaea27bed.tar.gz autocluster-55d315b1118283c60edaf365ef9b123eaea27bed.tar.xz autocluster-55d315b1118283c60edaf365ef9b123eaea27bed.zip | |
Remove NUMNODES and WITH_TSM_NODE configuration variables
The backward compatibility hacking is horrible!
Signed-off-by: Martin Schwenke <martin@meltin.net>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 12 |
1 files changed, 0 insertions, 12 deletions
@@ -440,18 +440,6 @@ Keep it simple CTDB cluster. It is just extra node that can be used as a test client or similar. - For many standard use cases the nodes specified by NODES can be - modified by setting NUMNODES and WITH_TSM_NODE. - However, these options can't be used to create nodes without - specifying IP offsets - except WITH_TSM_NODE, which checks to see if - IP offset 0 is vacant. Therefore, for many uses you can ignore the - NODES variable. - - However, NODES is the recommended mechanism for specifying the nodes - that you want in your cluster. It is powerful, easy to read and - centralises the information in a single line of your configuration - file. - iSCSI shared disks ================== |