On Tue, 2009-12-15 at 17:34 +0100, Patrick Ohly wrote: > As that doesn't seem to work, I'll look at using ABORTSESSION() in > addition to flagging individual datastores as "bad". If I can properly > abort the session without affecting "good" datastores then this might be > a suitable solution.
This works better, at least for the situation where one datastore is "good" and one is "bad". The whole session is aborted, later I can do a normal two-way sync with the "good" datastore alone. But when both datastores are told to do an unexpected slow sync, then only the first <alertscript> is executed, then the whole session is taken down immediately because of the ABORTSESSION() in it. For the second datastore I end up with the overall session status code instead of detecting the unexpected slow sync. Is there perhaps a possibility to invoke all <alertscripts>, then before starting to sync, call some other script and invoke ABORTSESSION() in it based on some session variable set by the other scripts? -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
