T.R | Title | User | Personal Name | Date | Lines |
---|
533.1 | Re: Problem with bco | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Wed Jan 26 1994 12:26 | 15 |
| Date Of Receipt: 24-JAN-1994 22:25:52.08
From: WASTED::jmf "Joshua M. Friedman ULTRIX SDE"
To: [email protected]
CC: odehelp@wasted:zko.dec
Subj: Re: Problem with bco
you're absolutely sure about the path?
setenvir_csh not setenvir.csh ? just a guess...
try adding -debug and/or -verbose and see if you get any more meaningful
information. Can you do a blog on the same file path?
-j
|
533.2 | Re: Problem with bco | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Wed Jan 26 1994 15:37 | 30 |
| Date Of Receipt: 26-JAN-1994 10:24:20.98
From: KRISIS::hantman "Paul C. Hantman OSG Test Tools"
To: Joshua M. Friedman ULTRIX SDE <krisis::jmf>
CC: [email protected], krisis::odehelp
Subj: Re: Problem with bco
Hi,
>you're absolutely sure about the path?
Yes.
>setenvir_csh not setenvir.csh ? just a guess...
The file is setenvir_csh
>try adding -debug and/or -verbose and see if you get any more meaningful
>information. Can you do a blog on the same file path?
Adding -debug and -verbose provides no additional useful information. I still
get the message "authcover exists"
When I try blog I get the following:
[ ./tte/decsuite/setenvir_csh ]
blog: The following rcs command failed:
authcover rlog -r ./tte/decsuite/setenvir_csh,v
-Paul
|
533.3 | Problem with bco | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Wed Aug 16 1995 18:23 | 33 |
| Date Of Receipt: 16-AUG-1995 16:47:35.40
From: SMURF::ALPHA::"[email protected]"
To: [email protected]
CC:
Subj: Problem with bco
I've never done one before and I was told I might need to
be added to some list, but here's the problem...
isaiah.zk3.dec.com-50> pwd
/home/jps/sb/ptos/src/usr/ccs/bin/gem
isaiah.zk3.dec.com-51> bsh ls
cd /usr/sde/osf1/build/ptos.nightly/src/usr/ccs/bin/gem
Makefile ptos_gemc_cc.Z
isaiah.zk3.dec.com-52> bco ptos_gemc_cc.Z
[ ./usr/ccs/bin/gem/ptos_gemc_cc.Z ]
ODE CLIENT: ERROR - Failed client authentication.
Have you done a kinit & workon?
bco: The following rcs command failed:
ode_client exists ./usr/ccs/bin/gem/ptos_gemc_cc.Z,v
[ unable to access source control information in file: "./usr/ccs/bin/gem/ptos_gemc_cc.Z,v" ]
Any help appreciated.
Thanks,
-Jeff
|
533.4 | re: Problem with bco | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Wed Aug 16 1995 18:27 | 64 |
| Date Of Receipt: 16-AUG-1995 17:04:43.45
From: SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE 16-Aug-1995 1703"
To: [email protected]
CC: odehelp@DEC:.zko.flume
Subj: re: Problem with bco
Jeff, here's a response sent earlier to someone else with the same
error message....
------- Forwarded Message
To: Dick Bagley USG <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: Having a problem...
In-Reply-To: Your message of "Wed, 16 Aug 95 11:36:35 EDT."
<[email protected]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 16 Aug 95 11:41:11 -0400
From: "Grant Van Dyck" <[email protected]>
X-Mts: smtp
Check you path to be sure it's not hardwired in someway to ode2.0. You might
try setting your path something like this:
set toolspath=( /usr/sde/tools/`machine`_`uname`/bin )
set path=( $path $toolspath /usr/ucb /bin /usr/bin /sbin /usr/sbin /etc
/usr/bin/X11 )
-Grant
| Hi -
|
| I'm now having a problem with my sandboxes attempting to do a "bstat -all".
|
| I get the following in response from ode:
|
| [SB]-hw5.bagley>bstat -all
|
| [ ./kernel/arch/alpha/hal/cbus2_pci.c ]
| ODE CLIENT: ERROR - Failed client authentication.
| Have you done a kinit & workon?
|
| [ There is no branch revison for set Dick_Bagley_hw5. ]
|
| Any clues ?? I do perform the kinit before entering the workon, so I haven
't
| a clue as to why this no longer works for me.
|
| THanks for any help.
|
| - dick bagley
------- End of Forwarded Message
|
533.5 | problem with bco | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Fri Aug 18 1995 18:23 | 29 |
| Date Of Receipt: 18-AUG-1995 16:45:14.75
From: SMURF::QUARRY::lae "LAURIE ANNA EDLUND USG 18-Aug-1995 1643"
To: odehelp@DEC:.zko.quarry
CC:
Subj: problem with bco
Hello,
I am unable to bco any file. The error I'm getting is:
bco: unable to lock via lockf() /tmp_mnt/home/lae/sandboxes/decx11/src/.BCSloc
k errno=77: No locks available
Same is true for ptx11 pool.
and bstat -all returns nothing in either pool.
Thank you!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Laurie Anna Edlund | enet: [email protected] *
* Digital Equipment Corp.| Unix Software Group *
* Spit Brook Road, NH | Mail Stop: ZKO3-2/W17 *
* (603) 881-2837 | (dtn) 381-2837 *
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
533.6 | problem with bco | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Fri Aug 18 1995 18:23 | 10 |
| Date Of Receipt: 18-AUG-1995 16:48:21.68
From: SMURF::ALPHA::"[email protected]" "18-Aug-1995 1347"
To: [email protected]
CC:
Subj: problem with bco
lea needs to see if the lock deamon is running on the server.
Hamid
|
533.7 | Re: problem with bco | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Mon Aug 21 1995 01:33 | 42 |
| Date Of Receipt: 20-AUG-1995 23:36:05.79
From: SMURF::QUARRY::"[email protected]"
To: [email protected]
CC: [email protected]
Subj: Re: problem with bco
Now that nfs locking is really in force, the src.BCSlock file in your sandbox
is really checked. If one exists, just delete it and try again.
-Grant
>
> Hello,
>
> I am unable to bco any file. The error I'm getting is:
>
> bco: unable to lock via lockf() /tmp_mnt/home/lae/sandboxes/decx11/src/.BCSloc
> k errno=77: No locks available
>
> Same is true for ptx11 pool.
>
> and bstat -all returns nothing in either pool.
>
> Thank you!
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> * Laurie Anna Edlund | enet: [email protected] *
> * Digital Equipment Corp.| Unix Software Group *
> * Spit Brook Road, NH | Mail Stop: ZKO3-2/W17 *
> * (603) 881-2837 | (dtn) 381-2837 *
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
>
--
Grant Van Dyck enet: [email protected]
Release Engineering
|