(sorry to the moderator--I bzip'ed this to shrink things down a hair. There really are not too many packets in this trace...)
Never fear! This happens so much now that I don't have to wait. I'm attaching one more trace before which I restarted the client (after wiping the cache partition). The cilent seemed to connect to the server well, until around packet #125 in the trace. From the trace it looks like it started to fail after a VLDB request/reply. Take a look. I am trying to get one other trace: I noticed this apparent last good packet was an encrypted vldb request/reply. I am trying to get the same trace without first obtaining tokens, thereby eliminating the possibility of making any such requests. Funny thing is, I haven't been able to see it happen yet. When the "lost contact" did occur, I did even attempt to list other users directories where I wouldn't have any rights, but everything seemed to emit a "Connection timed out" notice. I'll continue trying to see if the client behaves badly without obtaining tokens. If I can capture it, I'll post... Spencer On Sunday 21 August 2005 01:41, Derrick J Brashear wrote: > it needs to include the first error packet, e.g. the window where it loses > contact, to be useful > > once it's down, that's not interesting > > Derrick > > _______________________________________________ > OpenAFS-devel mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-devel
started-good-then-bad.cap.bz2
Description: BZip2 compressed data
pgpbwVKxe0EHo.pgp
Description: PGP signature
