Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site down
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!down!honey
From: honey@down (code 101)
Newsgroups: net.unix-wizards
Subject: Re: Making sense of LOGFILE
Message-ID: <164@down>
Date: Thu, 3-May-84 21:40:04 EDT
Article-I.D.: down.164
Posted: Thu May  3 21:40:04 1984
Date-Received: Fri, 4-May-84 04:19:46 EDT
References: <577@aplvax.UUCP>
Organization: The Official Fun Machine of Princeton Univ. EECS
Lines: 32

interpreting your log is complicated by the fact that milo.p and milo
are the same machine; the logs for both sides of the transaction are
merged into the same file.  splitting by pid into 2 logs simplifies
things.

the milo.p log: (you skipped the SUCCEEDED (call to milo) line ...)
	eric milo.p (3/19-15:44-3725) OK (startup)
initial handshake ok.
	eric milo.p (3/19-15:44-3725) REQUEST (S /etc/group /tmp/milogrp eric)
try to send milo.p!/etc/group -> milo!/tmp/milogrp
	eric milo.p (3/19-15:45-3725) REQUESTED (CY)
milo says it worked.
	eric milo.p (3/19-15:45-3725) OK (conversation complete)
hangup handshake ok.

the milo log:
	uucp milo (3/19-15:44-3150) /usr/spool/uucp/LCK.SQ (CAN'T LOCK)
this is an artifact of milo.p calling itself (but doesn't matter since
no one uses private sequence numbers anyway.)
	uucp milo (3/19-15:44-3150) OK (startup)
initial handshake ok.
	uucp milo (3/19-15:44-3150) REQUESTED (S /etc/group /tmp/milogrp eric)
try to receive milo!/tmp/milogrp <- milo.p!/etc/group 
	eric milo (3/19-15:44-3150) COPY (SUCCEEDED)
success.
	eric milo (3/19-15:45-3150) OK (conversation complete)
hangup handshake ok.

concerning your comment
	The source code is a rather obscure source of info.
we will probably never agree on this point.
	peter honeyman