ovdb_monitor

Ovdb_monitor really ought to remove its pid file when it exits... I 
just spent a chunk of the morning trying to figure out why I had a 
couple of hundred log files sitting around, and why when I ran 
ovdb_init it'd tell me that ovdb_monitor was already running.  Which it 
wasn't.

Finally the light dawned.  Turns out that after the last "ovdb hung and 
I have to reboot" cycle, my ovdb_monitor.pid file ended up with "652" 
in it, and now nfsd was pid 652... So ovdb_init was seeing that there 
was a pid file, and that that pid did exist.  Of course, it wasn't 
actually ovdb_monitor...

Once I deleted the pid file and started again the log files magically 
went away.  Apparently ovdb_monitor had exited at some point two days 
ago, and news was happily running along anyway until it mutex hung 
again... (Which, for the record, is happening about 5 times a week, 
during the expireover runs.)