Man I really learnt how to screw up RD today. I renamed an event in rdlogmanager without removing it from a clock. The. I lost all the events in y clock bar about 2-3.
So I figured I'll just launch rdamin and do a DB restore. Only it froze trying to a restore from a perfectly valid backup. Now rebooting the machine takes 5 minutes to hit he desktop I think it's rdadmin locking the machine up. I've waited until Suse finally booted with desktop sound ( so rd has failed to initialise in the background). I try to start rdadmin and it locks up for infinity at 80% CPU and MySQL at 9%. So question is, how do I completely kill the SQL database so it's empty and gone and attempt another restore? Do I nee to remove MySQL and set it all back up again and pray it restores? I'm looking at the DB file and it seems all in order but renaming that one event has now lead to everything nonfuctional oops. I'm still using 1.7.2 which has been a great workhorse but now my even rdairplay or other rd apps will respond or start. Never did I think a DB restore would be a DB disaster. Sent from my iPod _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
