stale lock files: best practice?

Thanks guys for that info.

I’m adding the gslist -c command to the boot script.
The only moment that should get run is in case of linux server (re)boot.

Johan

> On 25 Feb 2016, at 23:14, Dale Henrichs via Glass <[hidden email]> wrote:
>
> In addition to Richard's comments here are a few more comments from folks here at GemTalk Systems:
>
>  - I like deleting everything in the directory on operating system startup.
>
>  - A live stone, shrpcmonitor or  netldi will recreate it's .LCK
>    file if it is deleted by accident.  There could be a small delay,
>    so some logins could fail for a few seconds ...
>
> Dale
>
> On 02/25/2016 10:58 AM, Johan Brichau via Glass wrote:
>> Hi there,
>>
>> On a server crash and subsequent reboot, it may happen the stone does not want to start because of stale lock files.
>>
>> I want to avoid this manual action of removing stale lock files and I am wondering what the best practice is.
>>
>> Is it OK to remove the lock files in a system boot script?
>> Since I’m using monit I may also try to add to the stone start script?
>> What would happen if you remove lock files for a running stone?
>>
>> What are others doing?
>>
>> cheers
>> Johan
>> _______________________________________________
>> Glass mailing list
>> [hidden email]
>> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
> _______________________________________________
> Glass mailing list
> [hidden email]
> http://lists.gemtalksystems.com/mailman/listinfo/glass

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass