Conference smurf::buildhelp

Date Of Receipt: 	21-MAR-1995 17:31:16.20
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  21-Mar-1995 1730"
To: 	decwet::ode
CC: 	ddhill@DEC:.zko.flume, odehelp@DEC:.zko.flume
Subj: 	re: I don't like the looks of this...

DECwest (Jo?) can you help interpret these error messages please?

I agree with Dave, it doesn't look very good.  I've checked all the
files, the submits in the decx11 pool and rcs files in the rcs/x11
pool, and everything looks fine.

If I just 'co' the file directly in the rcs tree, there's no complaint:

    # co -rDECX11 lcPrTxt.c
    lcPrTxt.c,v  -->  lcPrTxt.c
    revision 1.1.3.2
    done

Thanks for any assistance you can offer.

-josh


------- Forwarded Message

To: odehelp
Subject: I don't like the looks of this...
Date: Tue, 21 Mar 95 17:14:14 -0500
From: "Dave Hill" <ddhill>
X-Mts: smtp


In the middle of my bsubmit....

[ ./xc/lib/X11/lcGeneric.c checked in onto branch 1.1.3 ]
[ ./xc/lib/X11/lcInit.c checked in onto branch 1.1.3 ]
client read failed1: Error 0
[ ./xc/lib/X11/lcPrTxt.c checked in onto branch 1.1.3 ]

[ ./xc/lib/X11/lcGeneric.c Rev 1.1.3.2 checked out ]
[ ./xc/lib/X11/lcInit.c Rev 1.1.3.2 checked out ]
client read failed1: No such file or directory
[ ./xc/lib/X11/lcPrTxt.c Rev 1.1.3.2 checked out ]


I can blog both files fine.

If I bco -u all 31 files I get :

[ ./xc/lib/X11/lcPrTxt.c ]
client read failed1: No such file or directory
[ ./xc/lib/X11/lcPrTxt.c Rev 1.1.3.2 checked out unlocked ]

# bco -u lcPrTxt.c

[ ./xc/lib/X11/lcPrTxt.c ]
client read failed1: No such file or directory
[ ./xc/lib/X11/lcPrTxt.c Rev 1.1.3.2 checked out unlocked ]

The file looks right after the bco and is right in the decx11 tree.

/Dave






+---------------------oOO--(_)--OOo------------------------+
|Dave Hill                (0 0)    Unix Software Group     |
|Mailstop: ZKO3-3/Y15     \//\/    (dtn) 381-2985          |
|Digital Equipment Corp.           (603 )881-2985          |
|110 Spitbrook Road       /\//\    enet: [email protected]|
|Nashua, NH 03062-2698    (0_0)    decnet: gooey::ddhill   |
+---------------------oOO--(_)--OOo------------------------+

- ------- End of Forwarded Message



------- End of Forwarded Message

Date Of Receipt: 	21-MAR-1995 18:32:23.35
From: 	SMURF::ALPHA::"[email protected]" "21-Mar-1995 1531"
To: 	"Dave Hill" <[email protected]>
CC: 	[email protected]
Subj: 	Re: I don't like the looks of this...

hi dave,

the "client read failed1" error message means that a socket read failed.
which one?  hard to tell right now.  for the next release, DECode II v3.0,
we've cleaned up the error messages so that we'll have a better idea of what's 
actually going on.

a read failure can have a number of reasons as in possible network
problems.

as long as you're getting the file alright i would not worry about it.

when did you start getting the error messages?  have they been prevalent?

jo

Date Of Receipt: 	22-MAR-1995 09:48:49.55
From: 	SMURF::WASTED::ddhill "Dave Hill   22-Mar-1995 0947"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: I don't like the looks of this...

I get it consistantly on ONE file. I just sent a AUTHCOVER_DEBUG=1
dump and a good file dump to odehelp. Maybe that will help.

/Dave



> 
> hi dave,
> 
> the "client read failed1" error message means that a socket read failed.
> which one?  hard to tell right now.  for the next release, DECode II v3.0,
> we've cleaned up the error messages so that we'll have a better idea of what'
s 
> actually going on.
> 
> a read failure can have a number of reasons as in possible network
> problems.
> 
> as long as you're getting the file alright i would not worry about it.
> 
> when did you start getting the error messages?  have they been prevalent?
> 
> jo

+-------------------------------------------------------------+
Dave Hill                         Unix Software Group
Mailstop: ZKO3-3/Y15              (dtn) 381-2985
Digital Equipment Corp.           (603)881-2985 
110 Spitbook Drive                enet: [email protected]
Nashua, NH 03062-2698             decnet: gooey::ddhill
+-------------------------------------------------------------+