The call could of course also be done from a validation callback, when you detect that some combination of values is bad - "inconsistent" sort of implies that kind of problem, but as far as I know SNMP uses the
inconsistentValue error also when a single object is bad "in itself". For a validation callback I would expect that the SNMP reply indicates that the node that is annotated with
tailf:validate is the problematic object.
Also, in most cases you should not need to call
confd_trans_seterr_extended() with CONFD_ERRCODE_INCONSISTENT_VALUE, or even
confd_trans_seterr(), at all, but instead rely on ConfD generating the proper error reply based on type restrictions (
length etc) or
must expressions in the YANG model.