2017-03-13 09:14 AEST by Arthur Barrett - The first few cvsnt server processes don't seem to initialise quite properly.

The audit code should 'check' that the connection is OK.  If it is not OK, then maybe it should terminate or 
retry?

This doesn't break the 'failsafe audit' - these processes will just fail any command the user tries to run - but it 
would be better to just wait if the database is about to start any second.  The problem is we don't really know 
if that is the case or not.

Also see bug 7121.

Note: this is probably better fixed by bug 6139, i.e.: by moving the dbms code into cvsmanager then 
cvsmanager can handle the connection to the dbms much more intelligently.