Genet
Personally I would like all possible client options to be set from the server.
The client option set mechanism is limited in that only one can be specified
and they cannot, for example, include one set in another.
At one time, I had a set of m4 macros (I'm from a unix background) that
Hi,
parametr Force has no affect to include/exclude in cloptset.
use q inclexcl client command to check resulting (cloptset+dsm.opt)
include/exclude in normal order (from top to bottom).
You will find that server include/exclude processed first.
Efim
> 13 июня 2018 г., в 16:43, Genet Begashaw
Thanks for your response, on the server side it was included by Optionset
with force=no, i tried to overwrite in the client side in dsm.opt file with
different mgmt class like shown below
include.systemstate ALL MC-mgmt-name
still did not work
Thank you
On Wed, Jun 13, 2018 at 9:37 AM
Genet:
For us it is simple: create a client option set with the list of
include/exclude rules with FORCE=NO. Complexity comes from number of client
options sets needed to support different platforms (Win 7, Win 10, OS X, macOS,
various Linux destroys) and determining which client option
Thank you
Genet Begashaw
