[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | USG buildhelp questions/answers |
|
Moderator: | SMURF::FILTER |
|
Created: | Mon Apr 26 1993 |
Last Modified: | Mon Jan 20 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2763 |
Total number of notes: | 5802 |
2029.0. "More re: Waiting for sandbox lock (with lockf())" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Jan 03 1996 17:53
Date Of Receipt: 3-JAN-1996 16:55:07.45
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 03-Jan-1996 1652"
To: wgao@DEC:.zko.flume
CC: odehelp@DEC:.zko.flume
Subj: More re: Waiting for sandbox lock (with lockf())
Katie, the information Sean provided is correct, and applies
to the case in which your sandbox is mounted over NFS.
Here's more about what's going on. In your sandbox there's
a file called <sandbox>/src/.BCSlock -- this is the file that
the lock is taken out on - it's used to coordinate activities
such that if you have multiple windows to the same sandbox,
possibly on different systems over NFS, the bco etc. operations
are all coordinated. Each time a bco, bci, etc starts up it
takes out an flock on .BCSlock and when it's done the lock
is removed. While there's a lock out you get the message you
reported.
If you somehow killed a bco (etc) process in the middle, then
the flock on the inode is still in effect. If you're sure
that you don't have another window or shell to the same sandbox
in operation elsewhere, you can just "rm .BCSlock" and then
retry the command. A new .BCSlock file will then be created;
the old inode of the old .BCSlock will still hang around until
you reboot and then it'll all get cleared up, but this will be
invisible to you. No need to reboot for this purpose.
-josh
------- Forwarded Messages
To: [email protected]
Cc: [email protected]
Subject: Waiting for sandbox lock (with lockf())
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 03 Jan 96 11:47:23 -0500
From: [email protected]
X-Mts: smtp
When I try to bco from my workon session in sandbox ptcde,
I get this message, and it never completes.
I have seen this problem in another sandbox also, but that
one seems ok now.
Can you pls tell me what this message means, and what to do
about it so that I can bco a file?
thanks,
Katie
------- Message 2
To: [email protected]
Cc: [email protected]
Subject: Re: Waiting for sandbox lock (with lockf())
Date: Wed, 03 Jan 96 14:59:41 -0500
From: "Sean Davidson, M/S ZK3-3/Z28, DTN 381-1937" <[email protected]>
X-Mts: smtp
Make sure you have the rpc.lockd and rpc.statd running on the system
you are trying to do the ode command on.
The following values must be set in your /etc/rc.config file to turn on
locking when you boot your system.
NFSLOCKING="1"
export NFSLOCKING
Sean
------- End of Forwarded Messages
T.R | Title | User | Personal Name | Date | Lines
|
---|