[Csync2] action executed while doing a dry-run

[Lars Ellenberg]

deliberately breaking the threading.
this would have been:
In-Reply-To: <20081009164714.3f4de476 at opensde.org>


On Thu, Oct 09, 2008 at 04:47:14PM +0200, Christian Wiese wrote:
> Hi folks,
> 
> while testing csync2 I noticed that actions are executed even in the
> case of a "dry-run" using 'csync2 -xd'.
> 
> Is that supposed to be the correct behavior?
> For me it makes no sense to trigger any action if the change isn't done
> at all ;)

I'm going through some mails which I marked as
"todo verify somewhen if I have the time" now...

just for the record...

yes, this is supposed to be the correct behaviour.

btw, this happens only for "do-local" actions.
locally, csync2 schedules and execute the actions when it detects the change
(inserts it into the the dirty database).
which has to be done even before the "dry run" update.

local actions are even run for a "csync2 -m"
(which you can do even if nothing has changed at all,
and which does not comunitcate with any peers).

this may sometimes not be desireable, but that is how it is.

remote actions are not executed during "dry run" updates,
they are only executed when actually updating the file.

that should probably be mentioned in the documentation somewhere.
or we may change the behaviour.
but when exactly should local actions be executed?
any suggestions?

-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.