Chris Majewski wrote: > Folks > I'm updating a bunch of rrd's. > I had to kill the update processes because they were tying up my > machine. > Now I'm getting "could not lock RRD". > Is there a way to break the locks?
What kind of locks? Normally a lock is removed when the process dies. If your OS (which OS?) does things differently, maybe you can find a directory or so where lock files are kept, or a file in the same directory as the .rrd file, or special permissions on the .rrd file. ---> don't <--- mail me to specify your OS. Even if I know this I cannot help. Next time you mail to the list, specify your OS. Read the manual pages. Perhaps they show you how locking works on your system. "man lockf" seems to be a candidate, with "man flock" as a good runner up. The manual page for lockf cannot be found in the rrdtool documentation, it is (or: should be) in your system documentation. If this all doesn't help, maybe you can copy the file to another directory or name, rename the original file then rename the copy back to the original name. Don't know it that'll work. Example: cp my.rrd my.backup mv my.rrd my.locked mv my.backup my.rrd Of course you don't do step 3 if step 1 and/or step 2 failed. Even then you do this at your own risc. Don't blame me if it goes wrong and you destroy your .rrd file. HTH -- __________________________________________________________________ / [EMAIL PROTECTED] [EMAIL PROTECTED] \ | work private | | My employer is capable of speaking therefore I speak only for myself | +----------------------------------------------------------------------+ | Technical questions sent directly to me will be nuked. Use the list. | +----------------------------------------------------------------------+ | http://faq.mrtg.org/ | | http://rrdtool.eu.org --> tutorial | +----------------------------------------------------------------------+ -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
