| Date Of Receipt: 16-AUG-1995 14:56:57.70
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 16-Aug-1995 1453"
To: Rich Larsen <[email protected]>
CC: [email protected]
Subj: Re: sandbox locking problem
Rich,
This just means that the lock on <sandbox>/src/.BCSlock still
exists from the ^C'd operation. All that's needed is to rm this
file, and the next b* operation will re-create it.
Locks on this file keep multiple b* operations going on in
different windows for the same sandbox in sync. It always worked
this way, but now with locking it's more robust.
-josh
>
> Someone <cntrl> C'd a bco of a file in a sandbox. When he tries to
> bco that file again he gets:
>
> Waiting for sandbox lock (with lockf())
>
> Does this mean his workstation is not using NFS locking?
>
> Thanks,
>
> Rich
> ================================================================
> Rich Larsen, M/S: UNX TCP/IP: [email protected]
> USSG/User Env. & Std. Group DECnet: UNXA::LARSEN
> Digital Equipment Corporation FAX: 908-577-6003
> 200 Route 9 North Voice: 908-577-6083
> Manalapan, New Jersey 07726 DTN: 462
|