Making sense of LOGFILE
code 101
honey at down
Fri May 4 11:40:04 AEST 1984
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
More information about the Comp.unix.wizards
mailing list