here are two traces I took earlier (saved from ethereal, so I'm guessing this is tcpdump format).

server-down.cap was taken during a 'fs checks' while the server was "lost"
server-up.cap was taken during a 'fs checks' while the server was "found"

Spencer


------------
Spencer Olson
Department of Physics
University of Michigan
[EMAIL PROTECTED]
http://www.umich.edu/~olsonse/
PGP Fingerprint: A452 312C 73DC 41EF 47F3  EE73 A898 B528 BAD2 0D0F
(See www.pgp.net or pgp.mit.edu for public keys to encrypt messages for me)
tel:  734-647-9030
tel:  734-763-2544
fax:  734-764-5153

user, n.:
        The word computer professionals use when they mean "idiot."
                        -- Dave Barry, "Claw Your Way to the Top"

[I always thought "computer professional" was the phrase hackers used
when they meant "idiot."  Ed.]

On Fri, 19 Aug 2005, Martin MOKREJ? wrote:

Post "tcpdump -i lo -vv -s 1500" (or whatever interface) results when it 
happens again.
M.

Spencer E Olson wrote:
(sorry if this comes twice, I forgot to subscribe with this email address)

I saw something like this earlier on the list and was wondering if
anyone (besides myself) has issues with a client losing "contact" with
the afsd.

_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel


Attachment: server-up.cap
Description: Binary data

Attachment: server-down.cap
Description: Binary data

Reply via email to