-
Notifications
You must be signed in to change notification settings - Fork 174
WBEM Flags #25
Comments
Hmm... would you want to be able to change these flags between calls to ExecQuery? If not, then adding a Once we have a way to get the flags, it should be as simple as changing the CallMethod to include the optional parameters:
|
Well the "normal" way of including the flags is when the ExecQuery method is called e.g.
Here are some resources that explain the reasoning for the flags: https://technet.microsoft.com/en-us/library/ee198934.aspx I tried modifying the code myself e.g. added a QueryFast method, when I passed in 16 as the flag value (wbemFlagReturnImmediately), it works, but passing in 32 (wbemFlagForwardOnly), it generates an "unspecified error", same if the combined value of 48 is passed in |
Picking this up a year later... I implemented this as well, to try out if it resolves the linked issue from wmi_exporter. See the diff here Still, would be interested to hear what you think! |
Is it possible to allow for flags when calling ExecQuery e.g. WBEM_FLAG_RETURN_IMMEDIATELY & WBEM_FLAG_FORWARD_ONLY, as this can significantly improve query performance?
The text was updated successfully, but these errors were encountered: