Any problems with Project Colo services should be sent to the appropriate mailing list.
Most of the configuration files in Project Colo are managed using the Revision Control System (RCS). It is important that you respect this, otherwise your changes may be lost when the next person goes to edit the file. A typical session would look like
$ sudo co -l db.example.com
db.example.com,v --> db.example.com
revision 1.1 (locked)
done
$ sudo vi db.example.com
$ sudo ci -u -wMYUSERNAME db.example.com
db.example.com,v <-- db.example.com
new revision: 1.2; previous revision: 1.1
enter log message, terminated with single '.' or end of file:
>> Added new secondary, ns0.example.org.
>> .
done
$
Naturally, you should substitute the file name for
db.example.com, and your user name for MYUSERNAME.
If you do get a message that the file is already locked, try to find out if
someone else is editing it before proceeding. Also check for uncommitted
changes using rcsdiff.