[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

1335.0. "removing a sandbox" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Mar 14 1995 11:46

Date Of Receipt: 	14-MAR-1995 11:37:36.12
From: 	SMURF::WASTED::schloss "Mike Schloss usg  14-Mar-1995 1136"
To: 	odehelp@DEC:.zko.wasted
CC: 	
Subj: 	removing a sandbox

I have an old sandbox backed by a backing tree which is no longer
available (ptx.bl2).  I remember being told to never just delete a
sandbox as it the reservations and checkins may come back to haunt
me.  Since the backing tree is no longer available, I cannot cancel
my reservations and delete my branches.  The data is all stale so
I really have no need for it.  I may want to reuse the sandbox name
at some time in the future though and want to avoid getting burned.
What do I do now?

Mike Schloss

T.RTitleUserPersonal
Name
DateLines
1335.1Re: removing a sandboxAOSG::FILTERAutomatic Posting Software - mail to flume::puckThu Mar 16 1995 11:0984
Date Of Receipt: 	16-MAR-1995 10:53:47.12
From: 	SMURF::WASTED::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	schloss@DEC:.zko.wasted
CC: 	odehelp@DEC:.zko.wasted
Subj: 	Re:  removing a sandbox

Mike,

What you need to do is manually back the sandbox to something that does
exist.  Since this is an x-r5 sandbox, I suggest backing it to an
existing x-r5 pool, like ptlitex; once your sandbox is manually backed
then you can resb to what you've backed to (ensures rc_files are 
correct); then you can do all the normal stuff - if you have check-outs
(even if they're checked in) that aren't outdated, then can be outdated,
then you can remove the sandbox "correctly":

% su
root# /usr/sde/odemount ptlitex
root# exit

% cd <sandbox_base>
% rm link
% ln -s /usr/sde/osf1/build/ptlitex link
% workon -sb <sbname>      /* this couldn't work before, and should now */

% resb ptlitex
% exit

If you have nothing checked out in need of outdating you can now do:

% mksb -undo <sbname>

Otherwise workon to the sandbox; the list of files you have out -- and
which have rcs branches which could conflict with future work -- are in:
<sandbox_base>/src/.BCSset-<Principal_Name_setname>.  If you don't deal
with sets you only have one of these and setname==sbname; if you have
multiple sets you need to work with each one separately to cleanup
using:  
	% workon -sb <sbname> <setname>

If you want to just get rid of everything you have, first unlock everything
that's locked:
	% bcs -u -wall  (-wall assumes you haven't manually chmod'd bco'd
				file modes; if you have just use -all)

Then outdate all your private branches & remove all bco'd the files:

	% bcs -o -all

Now you can exit and mksb -undo  the sandbox.

-josh


---------
>From schloss  Tue Mar 14 11:36:43 1995
Delivery-Date: Tue, 14 Mar 95 11:36:49 -0500
Return-Path: schloss
Received: from abelia.zk3.dec.com by flume.zk3.dec.com; (5.65/1.1.8.2/16Jan95-0946AM)
	id AA06808; Tue, 14 Mar 1995 11:36:43 -0500
Received: from mhs.zk3.dec.com by wasted.zk3.dec.com; (5.65 EXP 2/22/95 for V3.2/1.1.8.2/18Feb95-1123AM)
	id AA20586; Tue, 14 Mar 1995 11:36:18 -0500
Received: from localhost by mhs.zk3.dec.com; (5.65/1.1.8.2/23Feb95-0329PM)
	id AA12063; Tue, 14 Mar 1995 11:36:16 -0500
Message-Id: <[email protected]>
To: odehelp
Subject: removing a sandbox
Date: Tue, 14 Mar 95 11:36:15 -0500
From: schloss
X-Mts: smtp

I have an old sandbox backed by a backing tree which is no longer
available (ptx.bl2).  I remember being told to never just delete a
sandbox as it the reservations and checkins may come back to haunt
me.  Since the backing tree is no longer available, I cannot cancel
my reservations and delete my branches.  The data is all stale so
I really have no need for it.  I may want to reuse the sandbox name
at some time in the future though and want to avoid getting burned.
What do I do now?

Mike Schloss