[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

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

2224.0. "Why do I get this message?" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Mon May 06 1996 14:24

Date Of Receipt: 	17-APR-1996 10:04:29.68
From: 	SMURF::QUARRY::courtney "Don Courtney USG  17-Apr-1996 0953"
To: 	odehelp@DEC:.zko.quarry
CC: 	
Subj: 	Why do I get this message?

I am trying to review a change, that was bci'd by 
Jim Mchale (against the steel backing tree).  And I
get a lockf message.

yauw.zk3.dec.com:/usr/users/courtney/quarry/sb/inclink/src/usr/ccs/bin/ld
159 % bco -u -rJim_McHale_steel mipscoff.c
Waiting for sandbox lock (with lockf())

159 % bco -u -rJim_McHale_steel mipscoff.c
Waiting for sandbox lock (with lockf())

yauw.zk3.dec.com:/usr/users/courtney/quarry/sb/inclink/src/usr/ccs/bin/ld
160 % bco -u -r4.3.30.12 mipscoff.c
Waiting for sandbox lock (with lockf())

T.R Title User Personal
Name Date Lines

2224.1 Re: Why do I get this message? AOSG::FILTER Automatic Posting Software - mail to flume::puck Mon May 06 1996 14:31 40

T.R	Title	User	Personal Name	Date	Lines
2224.1	Re: Why do I get this message?	AOSG::FILTER	Automatic Posting Software - mail to flume::puck	`Mon May 06 1996 14:31`	40
	Date Of Receipt: 17-APR-1996 14:51:38.57 From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 17-Apr-1996 1443" To: courtney@quarry.zk3.dec.com CC: odehelp@DEC:.zko.flume Subj: Re: Why do I get this message? Don, this means there's an flock outstanding on your sandbox src/.BCSlock file. You probably ^C'd in the middle of some b* operation, and it's waiting for it to complete. You should find that any b* command (but build) will give the same message. If you have another workon session which really is in the middle of some command, that must first finish. If not, just remove the .BCSlock file and the next b* command will create a new one, and everything should work fine. -josh > > I am trying to review a change, that was bci'd by > Jim Mchale (against the steel backing tree). And I > get a lockf message. > > yauw.zk3.dec.com:/usr/users/courtney/quarry/sb/inclink/src/usr/ccs/bin/ld > 159 % bco -u -rJim_McHale_steel mipscoff.c > Waiting for sandbox lock (with lockf()) > > > 159 % bco -u -rJim_McHale_steel mipscoff.c > Waiting for sandbox lock (with lockf()) > > > yauw.zk3.dec.com:/usr/users/courtney/quarry/sb/inclink/src/usr/ccs/bin/ld > 160 % bco -u -r4.3.30.12 mipscoff.c > Waiting for sandbox lock (with lockf()) > >

Date Of Receipt: 	17-APR-1996 14:51:38.57
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  17-Apr-1996 1443"
To: 	courtney@quarry.zk3.dec.com
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: Why do I get this message?

Don, this means there's an flock outstanding on your sandbox src/.BCSlock
file.  You probably ^C'd in the middle of some b* operation, and it's 
waiting for it to complete.  You should find that any b* command (but build)
will give the same message.

If you have another workon session which really is in the middle of some
command, that must first finish.  If not, just remove the .BCSlock file
and the next b*  command will create a new one, and everything should work
fine.

-josh

> 
> I am trying to review a change, that was bci'd by 
> Jim Mchale (against the steel backing tree).  And I
> get a lockf message.
> 
> yauw.zk3.dec.com:/usr/users/courtney/quarry/sb/inclink/src/usr/ccs/bin/ld
> 159 % bco -u -rJim_McHale_steel mipscoff.c
> Waiting for sandbox lock (with lockf())
> 
> 
> 159 % bco -u -rJim_McHale_steel mipscoff.c
> Waiting for sandbox lock (with lockf())
> 
> 
> yauw.zk3.dec.com:/usr/users/courtney/quarry/sb/inclink/src/usr/ccs/bin/ld
> 160 % bco -u -r4.3.30.12 mipscoff.c
> Waiting for sandbox lock (with lockf())
> 
>