Redirect the output from 00.ctdb pfetch to stdout.
authorRonnie Sahlberg <ronniesahlberg@gmail.com>
Thu, 28 Oct 2010 02:34:33 +0000 (13:34 +1100)
committerRonnie Sahlberg <ronniesahlberg@gmail.com>
Thu, 28 Oct 2010 02:35:55 +0000 (13:35 +1100)
Normally, the config.tdb database would not exist, so we do not need
to spam syslog with a "config.tdb does not exist" message every time we start ctdb

config/events.d/00.ctdb

index 1389ae40606184c081624143db02f01afb9f5565..61f2031094932104faddd207efa8a4b929e5edd8 100755 (executable)
@@ -16,7 +16,7 @@ update_config_from_tdb() {
        # Pull optional ctdb configuration data out of config.tdb
        PUBLICADDRESSESKEY='public-addresses:node#'`ctdb -t 1 xpnn|sed -e "s/.*://"`
        rm -f $CTDB_VARDIR/state/public_addresses
-       ctdb pfetch config.tdb $PUBLICADDRESSESKEY $CTDB_VARDIR/state/public_addresses
+       ctdb pfetch config.tdb $PUBLICADDRESSESKEY $CTDB_VARDIR/state/public_addresses 2>/dev/null
        [ "$?" = "0" ] && [ `stat --format="%s" /etc/ctdb/state/public_addresses` != "0" ] && [ ! -z "$CTDB_PUBLIC_ADDRESSES" ] && {
                diff $CTDB_VARDIR/state/public_addresses $CTDB_PUBLIC_ADDRESSES >/dev/null 2>/dev/null
                [ $? = "0" ] || {