Conference smurf::buildhelp

1994.0. "Fwd: ODE CLIENT ERROR" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Dec 14 1995 15:22

Date Of Receipt: 	14-DEC-1995 10:59:14.31
From: 	SMURF::FLUME::demers "Joyce Demers  14-Dec-1995 1056"
To: 	odehelp@DEC:.zko.flume
CC: 	decwet::petkus
Subj: 	Fwd: ODE CLIENT ERROR

Would someone in ODE at ZSO please check this out?
ronyon seems to be fine here locally in ZK.

		Thanks,

			Joyce

~~~~~~~~

Brenda, as far as the build is concerned, the build will pick up the last 
version of the file that was submitted.

------- Forwarded Message

Return-Path: petkus@decwet.enet.dec.com 
Delivery-Date: Wed, 13 Dec 95 18:45:19 -0500
Return-Path: petkus@decwet.enet.dec.com
Received: from DECnet-Mail11.flume.zk3.dec.com by flume.zk3.dec.com; 
(5.65v3.2/1.1.8.2/16Jan95-0946AM)
	id AA24786; Wed, 13 Dec 1995 18:45:17 -0500
Date: Wed, 13 Dec 1995 18:45:17 -0500
Message-Id: <9512132345.AA24786@flume.zk3.dec.com>
From: petkus@decwet.enet.dec.com
To: demers@flume.enet.dec.com
Subject: can't check in a manpage

Joyce, 

I checked out a manpage a little while ago, and now I can't seem to check 
it in. 
Are you still planning a manpage build tomorrow morning?  If so, what will 
happen if this manpage is checked out?

This is the message:

slugbt 10 -> bci -m"edits on -p flag" mkfdmn.8

[ ./BASE/MEGASAFE/man8/mkfdmn.8 ]
ODE CLIENT ERROR: Failed call to: connect() Connection timed out
ODE CLIENT: Check with ode admin, the ode_server daemon could be down.
ODE CLIENT: DECode client will retry
Retrying connection to ronyon.zk3.dec.com: retry number 1
Retrying connection to ronyon.zk3.dec.com: retry number 2
                                                           


------- End of Forwarded Message