1.0.2 -> 1.0.3-1: config files don't get regenerated

[lbm]

(02-19-2010 01:12 PM)kilburn Wrote:  Try to check the files in /etc/ispcp/bind/*. If you detect file with bad CRLF, correct it and regenerate configuration files (there's a howto in the docs).

Thanks for your reply.
Unfortunately
find /etc/ispcp/bind -exec file "{}" ";" | grep CR
does not output any files with CRLF.

Should I still try to regenerate? Which files will be regenrated, by the way? Is it every config file? In that case I should backup /etc if this fails again... Is there some documentation on how this works internally? (this would stop me from asking these dumb questions )

And an UPDATE to my original Post:
Actually three files did not get regenerated during the update (the last one I spotted later, by watching the mail.logs)
/etc/apache2/sites-available/ispcp.conf
/etc/bind/named.conf
and now I found /etc/postfix/ispcp/domains was also empty. The other files in /etc/posftfix/ispcp were OK, though.

All this looks to me as if the config file generation did not iterate over the domains correctly (as I said, I'm not aware how this works internally ). If I got it right from kilburn's reply the files are generated using the templates and the stuff stored in the MySQL DB. Anyway, this would imply that the apache and postfix config files would be gone again after regenerating(?), wouldn't it?

Thanks a lot for any information!