| Date Of Receipt: 29-AUG-1996 16:30:07.96
From: FLUME::mkm "Michael Martin USG"
To: [email protected]
CC: odehelp@DEC:.zko.flume
Subj: Re: Problem with waiting for lock
Dave,
There is a file called .BCSlock in the source directory of your
sandbox. If you are sure that no other processes are running,
that may be using this file you can remove this file and then
continue with your bco.
Every ODE process will (lock and unlock) the .BCSlock file.
The message that you are getting ".......Waiting for sandbox lock"
could have been caused if some ODE process (that had a lock) was killed
and left the file in a indeterminate state.
A new .BCSlock file will get created once the old one is removed.
regards,
Mike Martin
|
| Date Of Receipt: 29-AUG-1996 16:54:14.00
From: KAMLIA::dcj "David Jedlinsky USG"
To: mkm@DEC:.zko.kamlia
CC: odehelp@DEC:.zko.kamlia
Subj: Re: Problem with waiting for lock
That did it. We were attempting to remove the file with 'bcs
-unlock', which, of course, waits for the lock - Catch-22.
'rm' worked, however.
Thanks.
-Dave Jedlinsky
|