Kbase P106151: Why you should remove any "rm <database>.lk" command from scripts
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
Why you should remove any "rm <database>.lk" command from scripts
GOAL:
Why you should remove any "del <database>.lk" command from batches
FIX:
Some database startup scripts include these lines
rm <dbname>.lk
proserve <dbname>
It is very dangerous to leave this "rm" (or "del" command) within a script and it should not be needed.
There was a time (V6, V7) when it was necessary to remove the database lock file (<database>.lk), after a machine crash for example, as Progress executable _mprosrv was never doing it. Now _mprosrv checks if the shared memory segment referenced in the database lock file exists and corresponds to a Progress database; if the .lk file is not containing information from a running Progress Database Broker then _mprosrv will suppress the "old" .lk file.