Data.fs.lock is a lock file. just like all lock files do, it signals that something is in use by a process (in this case it signals that Data.fs has been opened by a process). all that it contains is a number representing a process ID. you should not just delete it. it is an important item. it is recreated every time zope starts up, yes, but it should stay in place as long as the process that created it runs. if that backup person thinks a file of 3-5 characters length that contains all digits is a corrupt file that he cannot back up he should look for a different job ;) jens On Wednesday, July 31, 2002, at 06:07 , <belen@netcom.no> wrote:
Hi, I am having problems with Data.fs.lock. I have been reported by the person that makes the system's back up that the data.fs.lock file appears to be corrupted. I have made some research and I have found out that there is no need to backup this file, but they are requesting me another solution.
I was wondering if it is possible to delete it and recreate it. If so, how would I do it? Would this recreation be something automatic done by Zope at restart, or do I have to do it myself? Can I delete the data.fs.lock file and live without it? And last quetion, what is the purpose of data.fs.lock? I have not found any documentation at all explaining what is it for. (Appart that it is a database lock...though this can be self explanatory for some :-))
Thanks a lot for your time,
BelÈn