Conference smurf::buildhelp

1426.0. "ACL needs update, or should I switch backing trees?" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Apr 20 1995 18:22

Date Of Receipt: 	20-APR-1995 16:31:33.72
From: 	SMURF::WASTED::"[email protected]" "20-Apr-1995 1630"
To: 	[email protected]
CC: 	[email protected]
Subj: 	ACL needs update, or should I switch backing trees?

A week or so ago I began some research into a QAR against DECthreads.
I was using the ptliteos.bl2 backing tree and managed to bci a particular
module successfully -- no real intent of checking in, just wanted to be
sure I had all the access mechanisms in place.

[by the way, I'm a neophyte with ODE II, with a total of about 2 days
experience]

Now this week I decided to get more serious about submitting the change
that I had researched.  I am now getting:
$ bco cma_vm.c

[ ./usr/ccs/lib/DECthread/COMMON/cma_vm.c ]
[ unable to access source control information in file: "./usr/ccs/lib/DECthread/
COMMON/cma_vm.c,v"  ]

... I'm pretty sure I'm set with Kerberos:

$ klist
Ticket file:    /var/dss/kerberos/tkt/tkt9112
Principal:      Paul_Clark@ZONE

  Issued           Expires          Principal
Apr 20 15:40:25  Apr 21 01:40:25  krbtgt.ZONE@ZONE
Apr 20 15:41:07  Apr 20 23:41:07  kxct.buffer@ZONE

... so what's going on?  Am I supposed to use bco only from a backing tree
that is open for checkouts?  I thought there was just one submit tree no matter
which backing tree I used?  Or, do the project leaders expect you to ask to
renew an ACL every week or so?

thanks, pac