http://bugzilla.wpkg.org/show_bug.cgi?id=252
--- Comment #11 from Rainer Meier <r.me...@wpkg.org> ---
Actually it did not fall back since falling back introduces the risk to
evaluate a check differently than it would evaluate on client side.
I have changed this behavior now as it works fine for pure "host" type checks
since this information (except environment) is available in wpkg.xml.
Now WPKG will print an error if it cannot find the result of a check in
wpgk.xml but it will continue to evaluate it - with potentially inaccurate
results.
FIX: If previously executed check results cannot be found in wpkg.xml then
WPKG will still evaluate the check on local machine if in remote query
mode. This will work for "host" type checks but not for others like
registry, file, execute etc. The results in this case might be inaccurate
and not reflecting the real check evaluation on client side.
An error will be printed to the logs in this case.
Fixes bug 252. Thanks to Stefan Pendl.
FIX: Do not try to look up logical checks in previously executed checks in
wpkg.xml.
Fixes bug 252.
(not really tested by me)
--
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
