locking, permissions, data

[Henk van der Velden]

We have seen this issue two times when an existing installation of  
one of our apps was copied to a new server. I didn't understand how  
it could happen, but probably Peter is right and using the on-off  
switch instead of properly shutting down the application is the cause.

Maybe we could check for the existence of a .rev~ file, and if one  
exists, remove the corresponding .rev file and change the extension  
from rev~ to rev.

Kind regards,
Henk


On Jul 23, 2008, at 06:34 , use-revolution-request at lists.runrev.com  
wrote:

> Yes, this could be it.  They do every so often close it down using  
> the on-off
> switch, which invokes the shutdown procedure, but too fast for rev  
> to close
> and save properly.  Could be.  Thanks - at least it frees one from  
> worrying
> that someone is trying to use a text editor on it.
>
> Now what to do about it!  At least it is fairly easy to recover from.
>
> Peter
>
>
> Martin Baxter-4 wrote:
>>
>> Peter,
>>
>> I believe the .rev~ file is made by the revolution engine  
>> automatically
>> when you do a stack save. It is a backup of the exisiting stack file
>> prior to the save command. If the save is successful it is  
>> deleted, so
>> you only see it if something went wrong.
>>
>> Assuming this is correct, this would suggest that the stack save
>> operation is failing part way through, for some reason.