On Mon, Apr 6, 2009 at 1:16 PM, Barry Fawthrop <[email protected]> wrote:
> Derrick Brashear wrote: > > On Mon, Apr 6, 2009 at 12:59 PM, Barry Fawthrop <[email protected]> wrote: > > > >> Okay so a "thread timer" is called and another thread is called. > >> > >> I have tried sending the debug information but moderator rejected due to > >> size > >> > > > > sure. you put it in afs or the web and give us a url or a path, and it's > not > > huge. problem solved. > > > > > >> So I'm going try again to use personally > >> > >> > > My Server IP is 24.227.64.44 now where near the 182.179.15.100 > > > > what's the client's IP? is nat in play? > > > > > > > > > > Yes Nat is in play My client is 192.168.0.11 > > Wireshark on the client can see the packets being sent to the server > Kerberos and TGS > and the initial NameToId Request to the Server > > Wireshark sees multiple responses back from the server > but the client does not see them it must have already crashed. > > What more besides the trace given in the last email is required ? > i have no idea. i don't have time to decode the assembly and see what's up, and really, it's not worth spending a whole lot of time on lwp anyway; in the nearish future openafs will just use pthreads. if you want to do experimental stuff, that might be possible now: define USE_PTHREADS when building liblwp (e.g. in src/lwp) and then use that liblwp. or, better yet, stop linking liblwp, librx, librxkad and company and link (only) libafsrpc, libafsauthent, libafsutil and libpthread. -- Derrick
