Sanjay, You are worrying about the wrong thing. Whenever you start virtuoso, it will create a CDS.log file (typically in your home directory), and because virtuoso is writing it, it will lock it using the Cadence Locking System. This is what creates the CDS.log.cdslck file. This is so that if you start a second virtuoso, it will not try to write to the same log file - it will see that it's locked and create CDS.log.1 (and lock that). So these lock files are supposed to be created (and if it didn't, that would be a problem). Normally when either the file is closed or virtuoso exits, the lock is cleared. However, in the event of the crash, there's no chance to clean up the locks and so the lock files remain - but they are recoverable using the mechanism I described previously - there's no need to delete them. So you are confusing a symptom with the real problem - the fact that it crashes. You are using an unsupported version of Virtuoso, and it's highly likely that whatever problem is causing the crash has been resolved in the intervening time period. So my first suggestion would be to try a newer version, and if that's not successful, you should contact customer support (we'd need the crash log files with stack traces etc to help identify if it's known issue). By the way, it's generally considered bad practice to run applications (such as Virtuoso) as root. Too much danger of breaking your OS to run as root (you might accidentally delete things that are vital to the correct operation of the machine). Regards, Andrew.
↧