Known bugs:
-----------

Clone detection can give false warnings if a user connects and then signs
off several times in rapid succession.

Clone detection also goes off wrongly if a server links and has a number of
clients from the same hostname.

If there is absolutely no activity on your network, Services may delay
timed events (nick kills, database saving, etc.) until the next message
comes in from Services' uplink server.

If Services receives a SIGHUP or SIGTERM signal while processing a command,
save_xx_dbase() may be called with the database in an inconsistent state.
This can under some conditions cause Services to crash while saving,
resulting in corrupt database files (though the backup files will still be
available).
