Re: hierarchy.log format

pete@corp.netcom.net.uk writes:

>Is there a list of all the possible transaction types that occour in the
>hierachy.log file with explanations of what they mean?

I have added this to the Release-Notes for the upcoming official
1.0 version.

..............................................................................
Hierarchy Log Types:

        DEAD_NEIGHBOR A sibling has been detected as dead after
                                failing to reply to 20 consecutive ICP
                                queries.
        DEAD_PARENT A parent has been detected as dead.
        DIRECT The object has been requested from the origin
                                server.
        FIREWALL_IP_DIRECT The object has been requested from the origin
                                server because the origin host IP address is
                                inside your firewall.
        FIRST_PARENT_MISS The object has been requested from the
                                parent cache with the fastest weighted round
                                trip time.
        FIRST_UP_PARENT The object has been requested from the first
                                available parent in your list.
        LOCAL_IP_DIRECT The object has been requested from the origin
                                server because the origin host IP address
                                matced your 'local_ip' list.
        NEIGHBOR_HIT The object was requested from a sibling cache
                                which replied with a UDP_HIT.
        NO_DIRECT_FAIL The object could not be requested because
                                of firewall restrictions and no parent caches
                                were available.
        NO_PARENT_DIRECT The object was requested from the origin server
                                because no parent caches exist for the URL.
        PARENT_HIT The object was requested from a parent cache
                                which replied with a UDP_HIT.
        REVIVE_NEIGHBOR A sibling cache was detected as alive again.
        REVIVE_PARENT A parent cache was detected as alive again.
        SINGLE_PARENT The object was requested from the only
                                parent cache appropriate for this URL.
        SOURCE_FASTEST The object was requested from the origin server
                                because the 'source_ping' reply arrived first.
        UDP_HIT_OBJ The object was received in a UDP_HIT_OBJ reply
                                from a neighbor cache.

Please let me know if that needs more clarification.

Duane W.
Received on Mon Jul 01 1996 - 08:12:54 MDT