fpolicy-policy-scope-{create,modify} surprising behaviour when adding shares-to-include.

ADRIAN_PYBUS — Thu, 05 Jun 2025 05:44:17 GMT

When running

na_elem_t* top_node = na_elem_new("shares-to-include);

na_child_add_string(top_node, "string", "File root");

na_child_add(inElem,top_node);

expecting to get

<shares-to-include>

</shares-to-include>

but then actually got

<shares-to-include>

</shares-to-include>

The 'documentation' for na_child_add_string seems to indicate that we should only get one item.

By adding double quotes around the share name we get the expected behaviour.

The processing of na_child_add_string for shares-to-include differs from other places, i.e. when setting engine name you can't have double quotes around it.

Re: fpolicy-policy-scope-{create,modify} surprising behaviour when adding shares-to-include.

aashray — Tue, 11 Feb 2014 05:42:26 GMT

Agreed. I'll look into it. Will request a fix in the documentation if necessary. Thank you for pointing it out.

topic Re: fpolicy-policy-scope-{create,modify} surprising behaviour when adding shares-to-include. in Software Development Kit (SDK) and API Discussions

fpolicy-policy-scope-{create,modify} surprising behaviour when adding shares-to-include.

Re: fpolicy-policy-scope-{create,modify} surprising behaviour when adding shares-to-include.