[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

2736.0. "shared sandbox questions." by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Dec 19 1996 12:08

Date Of Receipt: 	19-DEC-1996 11:28:58.86
From: 	ALPHA::"[email protected]" "Bruce Lutz USG"
To: 	[email protected]
CC: 	
Subj: 	shared sandbox questions.

1. I have changed my shared sandbox server from lsmtemp to
   to lsmtest.  The shared sandbox no longer works.  What
   should I do?  Note: the new server works if I rename it
   to lsmtemp, but I would prefer to use lsmtest.

2. We are currently backed against ptos.bl12.  We want to be
   backed against ptbos.ssb.  My understanding of how I should
   accomplish this is as follows:

	snaptrack /usr/sde/osf1/build/ptos.bl12/logs/SNAPSHOT \
                  /usr/sde/osf1/build/ptbos.ssb/logs/SNAPSHOT \
                  /path/to/my/pool/logs/SNAPSHOT

   merge using the following syntax:

        bco -jPTOS_BL12:PTBOS_SSB file [file ...]

   Run the following in my shared sandbox:

        resb ptbos.ssb

3. Is it possible to save state prior to backing against ptbos.ssb?
   In case there is a problem, I would like to be able to get back
   where I was, with minimal pain.

T.RTitleUserPersonal
Name
DateLines
2736.1Re: shared sandbox questions.AOSG::FILTERAutomatic Posting Software - mail to flume::puckThu Jan 02 1997 14:1754
Date Of Receipt: 	19-DEC-1996 15:44:53.01
From: 	HUNCH::"[email protected]"
To: 	[email protected] (BRUCE LUTZ USG)
CC: 	[email protected], [email protected]
Subj: 	Re: shared sandbox questions.

> 
> 1. I have changed my shared sandbox server from lsmtemp to
>    to lsmtest.  The shared sandbox no longer works.  What
>    should I do?  Note: the new server works if I rename it
>    to lsmtemp, but I would prefer to use lsmtest.
> 

grep through your rc_files for any references to lsmtemp. You should find
references to submit_host and source_host.

You didn't specify what "no longer works" means, so this would be my first
guess. I assume the machine has a valid etc/srvtab file from admin?


> 2. We are currently backed against ptos.bl12.  We want to be
>    backed against ptbos.ssb.  My understanding of how I should
>    accomplish this is as follows:
> 
> 	snaptrack /usr/sde/osf1/build/ptos.bl12/logs/SNAPSHOT \
>                   /usr/sde/osf1/build/ptbos.ssb/logs/SNAPSHOT \
>                   /path/to/my/pool/logs/SNAPSHOT
> 
>    merge using the following syntax:
> 
>         bco -jPTOS_BL12:PTBOS_SSB file [file ...]
> 
>    Run the following in my shared sandbox:
> 
>         resb ptbos.ssb
> 


This is all good, BUT ptbos.ssb is just a convenience link pointing to the
real tree ptbos.bl4, therefore there is no branch label PTBOS_SSB only
PTBOS_BL4.

> 3. Is it possible to save state prior to backing against ptbos.ssb?
>    In case there is a problem, I would like to be able to get back
>    where I was, with minimal pain.
> 
> 

tar or vdump, take your pick. Once you throw the switch, there's no magic
return path.
-- 

				-Grant

2736.2Re: shared sandbox questions.AOSG::FILTERAutomatic Posting Software - mail to flume::puckThu Jan 02 1997 14:1974
Date Of Receipt: 	19-DEC-1996 17:33:24.89
From: 	FLUME::jmf "Joshua M. Friedman Digital UNIX"
To: 	bal@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: shared sandbox questions.

1. Bruce, did you change the settings of source host and submit host in
the shared sandbox's rc_files?  Do you have a new srvtab in /etc
created for the new hostname (run strings /etc/srvtab to read it)?

Once you complete these two actions, and restart workon sessions, it
should work.

2. There is no _SSB symbol for any pool; the .ssb links are provided as a
convenience to make it easy to avoid having to remember what was the ssb
baselevel, and mksb & snaptrack will accept the link name, however when
you need to refer to an rcs symbol, you must use the real POOL_BL#
symbol.  To do this, cd to /usr/sde/osf1/build/ptbos.ssb, then do a pwd
(in csh or sh; ksh will still say the .ssb name), to find out "where you
are".  Then use this real bl in the bmerge instructions, which are
otherwise correct.

3. All that the resb does, in addition to updating 'link', is to re-create
"shared" and "local" in the shared sandbox, saving the originals with a
.BAK suffix, but it will only save one such copy.  The new files are
generated from the backingtree's shared.tmpl and local.tmpl.  Another resb
back will just regenerate these again; if you haven't customized them,
there's nothing to be lost, however you could save a copy of the rc_files
directory prior to the first resb to be sure you put everything back as it
was.

-josh


------- Forwarded Message

Return-Path: [email protected] 
Delivery-Date: Thu, 19 Dec 96 11:25:31 -0500
Return-Path: [email protected]
Date: Thu, 19 Dec 1996 11:25:13 -0500
From: BRUCE LUTZ USG <[email protected]>
X-Mailer: Mozilla 3.0 (X11; I; OSF1 V4.0 alpha)
Mime-Version: 1.0
To: [email protected]
Subject: shared sandbox questions.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

1. I have changed my shared sandbox server from lsmtemp to
   to lsmtest.  The shared sandbox no longer works.  What
   should I do?  Note: the new server works if I rename it
   to lsmtemp, but I would prefer to use lsmtest.

2. We are currently backed against ptos.bl12.  We want to be
   backed against ptbos.ssb.  My understanding of how I should
   accomplish this is as follows:

	snaptrack /usr/sde/osf1/build/ptos.bl12/logs/SNAPSHOT \
                  /usr/sde/osf1/build/ptbos.ssb/logs/SNAPSHOT \
                  /path/to/my/pool/logs/SNAPSHOT

   merge using the following syntax:

        bco -jPTOS_BL12:PTBOS_SSB file [file ...]

   Run the following in my shared sandbox:

        resb ptbos.ssb

3. Is it possible to save state prior to backing against ptbos.ssb?
   In case there is a problem, I would like to be able to get back
   where I was, with minimal pain.