Martin Schwenke d44fed601d ctdb-tools: Avoid filtering stderr when onnode not running in parallel ... stderr_filter() only does anything useful when running in parallel (i.e. with the -p option). So, simplify the non-parallel case by not using stderr_filter(). As a side-effect, this fixes an issue introduced in commit 85a4375788 where local daemon tests would hang when trying to start daemons with VALGRIND set (to a valgrind command that does not use --log-file). This is because valgrind would keep stderr open for its output so the pipeline involving stderr_filter() would never complete. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>		2018-04-27 06:53:16 +02:00
..
ctdb_diagnostics	ctdb-tools: Remove duplicate code	2017-08-14 09:00:45 +02:00
ctdb_event.c	ctdb-build: Split protocol-util as a separate subsystem	2017-09-19 13:30:26 +02:00
ctdb_killtcp.c	ctdb-tools: Fix a typo for a talloc context	2017-09-19 17:31:18 +02:00
ctdb_lvs	ctdb-scripts: Split CTDB configuration loading	2018-03-28 02:57:20 +02:00
ctdb_natgw	ctdb-scripts: Avoid shellcheck SC1117: Backslash is literal in "..."	2018-04-27 06:53:16 +02:00
ctdb.c	ctdb: Fix some -Werror=strict-overflow issues	2018-04-27 06:53:16 +02:00
ltdbtool.c	ctdb-tools: Simplify using a local variable	2016-10-27 23:53:13 +02:00
onnode	ctdb-tools: Avoid filtering stderr when onnode not running in parallel	2018-04-27 06:53:16 +02:00