>>>>> " " == Christian Reis <kiko@async.com.br> writes:
>> > kernel:Aug 10 17:39:22 anthem kernel: lockd: cannot
>> > monitor 192.168.99.7
>>
>> Means that the kernel was unable to contact rpc.statd, or that
>> was unable to contact the server's rpc.statd for some reason.
> Hmmm, I wonder if I understand properly. Is the following flow
> correct for the RPC request?
> Client Kernel -> Client rpc.statd -> Server rpc.statd ->
> Server Kernel
That's more or less right, except that the communication is bidirectional.
>> lies with rpc.statd. Can you see any reason in your setup why
>> it should be failing?
> Not really. The clients run rpc.statd 1.0 and the server,
> 1.0.1. Should I start gdbing it to see what is going wrong?
Start by using tcpdump to find out who, in the above chain, is taking
such a long time to respond.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:42 EST