The module was not using the CONFIG_FILE object when updating files in /etc/xinetd.d. Those file were not archived when updated. So it was not possible to:
There is another flaw which will be fixed in the next release. The module do not support the disable keyword as people expect. It encodes in the file /etc/xinetd.conf, using the disabled keyword the list of disabled services. This is kind of incompatible with the way people are using xinetd server now. This will be changed in 1.29r2.