[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

2574.0. "Problem in creating sandbox on a ode-client." by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Sep 17 1996 12:15

Date Of Receipt: 	17-SEP-1996 10:58:08.53
From: 	HUNCH::"[email protected]" "17-Sep-1996 2026"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Problem in creating sandbox on a ode-client.

Hi,

        We are having problem creating a sandbox on a ode-client.

        We have configured ganges.xko.dec.com as the ode-client and
        waves.xko.dec.com as the ode-server.

        The client installation on ganges was verified by using check_ode -

        > # check_ode
        > Check_ode for DECode II V3.0 -- $Revision: 1.1.14.3 $
        > Tue Sep 17 19:00:48 GMT+0500 1996
        > Using logfile=tmp1723.logfile
        > 
        >    Info -- Checking Client:  ganges.xko.dec.com
        >    Info -- ganges.xko.dec.com: DECode II client Load=0
        >    Info -- Checking nfs locks on ganges.xko.dec.com
        >    Info -- not currently in a sandbox
        > 
        >    Client/sandbox  error count is 0

        If we try to create the sandbox using the command mksb, it asks for the
        absolute path of the backing tree.

Here is the log of the proceedings.
===================================

ganges.xko.dec.com> uname -a
OSF1 ganges.xko.dec.com V4.0 386 alpha
ganges.xko.dec.com> ls /usr/sde/osf1/build
ptaos.bl2              ptos.bl12              v32csupportos
ptliteos               steelos                v32csupportos.nightly
ptliteos.bl6           steelos.nightly
ganges.xko.dec.com> mksb -back steelos.nightly -dir ~/sbox -verbose st_tmp
User rc file, /home/indus/mohan/.sandboxrc, does not exist; will create it.
>> WARNING in mksb:
>> steelos.nightly is not a known backing tree.
>> Will prompt for this information.
>  Name of default set will match sandbox name: st_tmp.
>  Name of sandbox will be: st_tmp.
>  Sandbox directory and name will be: /home/indus/mohan/sbox/st_tmp.
No known current backing trees to pick from. 
Enter absolute path to backing tree: /usr/sde/osf1/build/steelos.nightly
>> WARNING in mksb:
>> /usr/sde/osf1/build/steelos.nightly is not a known backing tree.
>> Will prompt for this information.
No known current backing trees to pick from.
Enter absolute path to backing tree:

        Please help us resolving this error.

Thanks,
-Mohan

T.RTitleUserPersonal
Name
DateLines
2574.1Re: Problem in creating sandbox on a ode-client.AOSG::FILTERAutomatic Posting Software - mail to flume::puckTue Sep 17 1996 17:3298
Date Of Receipt: 	17-SEP-1996 15:26:48.89
From: 	FLUME::jmf "Joshua M. Friedman Digital UNIX"
To: 	[email protected], [email protected]
CC: 	
Subj: 	Re:  Problem in creating sandbox on a ode-client.

Mohan,

> If we try to create the sandbox using the command mksb, it asks for the
> absolute path of the backing tree.

You need to add the pool names & paths to /usr/sde/build_list to allow
just the pool or tree name to be used with the mksb command.

The format in the build list can be:
	tree <> /usr/sde/osf1/build

(the '<>' is a placeholder for an rcs date/time stamp, which is unused)

Today without the build_list entries, you should be able to, eg:

    mksb -back /usr/sde/osf1/build/ptaos.bl2 my_sandbox

With the addition of this line in /usr/sde/build_list:
    ptaos.bl2 <> /usr/sde/osf1/build

you should be able to do:
    mksb -back ptaos.bl2 my_sandbox

-Josh

-----------
From [email protected]  Tue Sep 17 10:57:11 1996
Delivery-Date: Tue, 17 Sep 96 10:57:25 -0400
To: [email protected]
Cc: [email protected]
Subject: Problem in creating sandbox on a ode-client. 
Date: Tue, 17 Sep 96 20:26:14 +0530
From: [email protected]
X-Mts: smtp


Hi,

        We are having problem creating a sandbox on a ode-client.

        We have configured ganges.xko.dec.com as the ode-client and
        waves.xko.dec.com as the ode-server.

        The client installation on ganges was verified by using check_ode -

        > # check_ode
        > Check_ode for DECode II V3.0 -- $Revision: 1.1.14.3 $
        > Tue Sep 17 19:00:48 GMT+0500 1996
        > Using logfile=tmp1723.logfile
        > 
        >    Info -- Checking Client:  ganges.xko.dec.com
        >    Info -- ganges.xko.dec.com: DECode II client Load=0
        >    Info -- Checking nfs locks on ganges.xko.dec.com
        >    Info -- not currently in a sandbox
        > 
        >    Client/sandbox  error count is 0

        If we try to create the sandbox using the command mksb, it asks for the
        absolute path of the backing tree.

Here is the log of the proceedings.
===================================

ganges.xko.dec.com> uname -a
OSF1 ganges.xko.dec.com V4.0 386 alpha
ganges.xko.dec.com> ls /usr/sde/osf1/build
ptaos.bl2              ptos.bl12              v32csupportos
ptliteos               steelos                v32csupportos.nightly
ptliteos.bl6           steelos.nightly
ganges.xko.dec.com> mksb -back steelos.nightly -dir ~/sbox -verbose st_tmp
User rc file, /home/indus/mohan/.sandboxrc, does not exist; will create it.
>> WARNING in mksb:
>> steelos.nightly is not a known backing tree.
>> Will prompt for this information.
>  Name of default set will match sandbox name: st_tmp.
>  Name of sandbox will be: st_tmp.
>  Sandbox directory and name will be: /home/indus/mohan/sbox/st_tmp.
No known current backing trees to pick from. 
Enter absolute path to backing tree: /usr/sde/osf1/build/steelos.nightly
>> WARNING in mksb:
>> /usr/sde/osf1/build/steelos.nightly is not a known backing tree.
>> Will prompt for this information.
No known current backing trees to pick from.
Enter absolute path to backing tree:

        Please help us resolving this error.

Thanks,
-Mohan