1. Reinstalling domtool
In the case that you make changes to domtool and want to reinstall it, see DomTool/Building, the Reinstalling the standalone tools section, for instructions.
2. Validating after a major change
If something changes in the Domtool standard library, users' configuration might stop working. If you just run domtool-admin regen in such a case, those users' domains will go down, which will probably make them sad. Instead, run this first:
domtool-admin regen -tc
This just verifies that all configuration type-checks. You can go through and fix the errors, which show up in /var/log/domtool.log on deleuze, one at a time, and only run domtool-admin regen (as in the following section) after everything type-checks.
3. Regenerating files
To effectively erase all published configuration and regenerate it all by running all files found in .domtool subdirectories of users' AFS volumes, run:
domtool-admin regen
You might want to do this if there has been some nasty kind of data corruption, or if a security vulnerability has been discovered in DomTool and you want to drop all old, unsafe configuration directives that the buggy DomTool had been letting through.
4. Regenerating user-specific files
Domtool contains support for generating certain files whenever the set of users changes. For now, the only file is /etc/apache2/waklog.conf, which assigns a Kerberos principal to every user's /~ URL.
Normally this file is regenerated whenever a user is added or removed. If you need to trigger a manual regeneration, run:
domtool-admin reusers