| Date Of Receipt: 6-JUL-1994 14:00:29.45
From: FLAMBE::jmf "Joshua M. Friedman OSF/UNIX SDE 06-Jul-1994 1358"
To: [email protected]
CC: odehelp@DEC:.zko.flambe
Subj: Re: Having a problem with ode and backing trees.
Tony, one problem which you may be seeing is that if you've created
the trees in group 'staff' (or some other group) as we do, and the
rc_files or logs or src directories of the tree don't allow read
to the world (as they really shouldn't), then all users need to be
in group 'staff' (or whatever) to read the control files. Otherwise
they will get exactly the message you got.
Just yesterday I helped someone with this problem -- adding the group
staff (in our case) with the user as a member in /etc/group and
re-logging-in fixed the problem.
-josh
------- Forwarded Message
Return-Path: [email protected]
Delivery-Date: Wed, 06 Jul 94 11:59:23 -0400
Return-Path: [email protected]
Received: from peewee.unx.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
id AA05160; Wed, 6 Jul 1994 11:57:22 -0400
Received: by peewee.unx.dec.com (5.57/MS-040293);
id AA26946; Wed, 6 Jul 94 11:57:21 -0400
Received: from localhost by daffy.unx.dec.com; (5.65/1.1.8.2/26May94-0237PM)
id AA07123; Wed, 6 Jul 1994 11:57:20 -0400
Message-Id: <[email protected]>
To: [email protected]
Subject: Having a problem with ode and backing trees.
Date: Wed, 06 Jul 94 11:57:19 -0400
From: [email protected]
X-Mts: smtp
Hi,
I'm trying to use ode to maintain some source code which myself and
people in my group are working on for platinum.
I followed all of the directions in the DEC ODE Project Admin Guide
and the directions we have online here on setting up an ode system to be
server/client. I did not however do any setups for the system to be a
kerberos server.
I can make sandboxes against my newly created backing tree (in reality
this is the actual submit tree). In that sandbox I can do bci's, bco's,
bsubmit's etc. etc. etc. No problem.
I then went, on the system where the backing/submit tree is, and
attempted to make a second backing tree (a 'nightly' tree) using the mkback
command. No errors were reported. My problem is that I can not make a
sandbox backed against this nightly tree. Mksb says that it is not a legal
accessible sandbox.
At the end of the mail are some wierd observations which I have
made. Maybe they will mean something to you.
What am I doing wrong? What have I forgotten?
Any help you can provide would be greatly appreciated.
Thanks
Tony D.
daffy.unx.dec.com > mksb -back /gui/desktop/back/build/dtapps.nightly test_ni>
>> WARNING in mksb:
>> could not get project directory or default build.
>> WARNING in mksb:
>> /gui/desktop/back/build/dtapps.nightly is not a legal, accessible sandbox.
>> Will prompt for this information.
No known current builds to pick from.
Enter absolute path to backing tree or name from build list:
/gui/desktop/back/build/dtapps.nightly
>> WARNING in mksb:
>> /gui/desktop/back/build/dtapps.nightly is not a legal, accessible sandbox.
>> Will prompt for this information.
No known current builds to pick from.
Enter absolute path to backing tree or name from build list:
If however I make a sandbox against my 'submit tree', and then attempt
to make a second sandbox against my nightly tree, mksb at least recognizes
that both sandboxes exist, but it still will not let me create the sandbox.
daffy.unx.dec.com > mksb -back /gui/desktop/back/build/dtapps test
>> WARNING in mksb:
>> could not get project directory or default build.
creating new set: Anthony_Decarlo_test, setdir: .
creating lock file for new set.
[ creating /u1/sandboxes/test/tmp ]
/u1/sandboxes/test/tmp: created directory
drwxr-xr-x 2 td system 512 Jul 6 11:50 /u1/sandboxes/test/tmp
daffy.unx.dec.com >
daffy.unx.dec.com >
daffy.unx.dec.com > mksb -back /gui/desktop/back/build/dtapps.nightly test_ni>
>> WARNING in mksb:
>> /gui/desktop/back/build/dtapps.nightly is not a legal, accessible sandbox.
>> Will prompt for this information.
Enter name of backing tree: from the known list or a complete path
or a name from the build list.
Known current builds include:
dtapps dtapps.nightly
HERE IT NOW RECOGNIZES THAT THE SECOND BACKING TREE EXISTS, DTAPPS.NIGHTLY,
BUT I CAN NOT BACK AGAINST IT.
Backing tree? <dtapps> dtapps.nightly
>> WARNING in mksb:
>> /gui/desktop/back/build/dtapps.nightly is not a legal, accessible sandbox.
>> Will prompt for this information.
Enter name of backing tree: from the known list or a complete path
or a name from the build list.
Known current builds include:
dtapps dtapps.nightly
Backing tree? <dtapps> /gui/desktop/back/build/dtapps.nightly
>> WARNING in mksb:
>> /gui/desktop/back/build/dtapps.nightly is not a legal, accessible sandbox.
>> Will prompt for this information.
Enter name of backing tree: from the known list or a complete path
or a name from the build list.
Known current builds include:
dtapps dtapps.nightly
Backing tree? <dtapps>
The next bizarre thing is that we do have here another system,
roadrunner, which is used by another group. On roadrunner, they have previously
performed the same task that I am attempting. They have not however attempted
to created a 'nightly' backing tree however. They always back their sandboxes
to the actual submit tree for there code.
The point is, that if I login to roadrunner and try to make sandboxes
backed against my backing tree. It works!!! It works for the submit tree
AND the nightly tree which I created.
------- End of Forwarded Message
|
| Date Of Receipt: 30-NOV-1995 14:44:03.74
From: SMURF::US2RMC::"[email protected]"
To: [email protected]
CC: [email protected]
Subj: problem with ode
Josh, 2 days ago, I bco'd /src/usr/sbin/tftpd/tftpd.c from
v32csupportos.nightly pools.
Today, I want to bci the changed file in but get "access denied by ACL"
no matter what I do.
I re-kinit, tried bcs -o, etc but nothing is working.
Can someone help?
principal = Bob_Spear
% Received: from pannik.zk3.dec.com by us2rmc.zko.dec.com (5.65/rmc-22feb94) id AA19772; Thu, 30 Nov 95 14:31:42 -050
from localhost by pannik.zk3.dec.com; (5.65v3.0/1.1.8.2/28Mar95-0117PM) id AA09730; Thu, 30 Nov 1995 14:33:46 -050
% Message-Id: <[email protected]>
% To: [email protected]
% Cc: [email protected]
% Subject: problem with ode
% Date: Thu, 30 Nov 95 14:33:45 -0500
% From: [email protected]
% X-Mts: smtp
|