A bunch of questions about commitinfo

[Marc Haber]

Hi,

I work at an ISP, and we are using cvs to aid in the configuration of
DNS zones. This has been in production for a year and works fine.
However, I'd like to add some more levels of control and ease to the
system:

- feeding committed data to a test name server and reject the commit
if that data causes the name server to emit error message
- build name server configuration files from the committed data
- build reverse zones from the forward data
- trigger the "real" name servers to check out the newly committed
data and to reload

I feel that commitinfo is the correct place to do this. However, I
would like to ask if somebody has already done this and might care to
share experiences.

Am I allowed to make changes to the repository in my commitinfo
script? Do I have to take special care to do so without damaging
metadata? Or is there a special procedure to be followed if I intend
to make changes during my commitinfo script?

Does the user committing see the output of my commitinfo script?

Any hints will be appreciated. Thanks in advance.

Greetings
Marc

-- 
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber          |   " Questions are the         | Mailadresse im Header
Karlsruhe, Germany  |     Beginning of Wisdom "     | Fon: *49 721 966 32 15
Nordisch by Nature  | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29