Hi, Two things..... I got: lockd: cannot monitor <client> in the logfile and the client was terrily slow/not working at all. everything pointed to a lockd problem... In the end... it turns out that my rpc.statd stopped working. I had to go and download the sources to figure this out... I would firstly suggest to improve the error message to give others running into this more hints as to where to look. The erorr message on line 169 of lockd.c could read: lockd: Error in the rpc to rpc.statd to monitor %s\n Would it be an idea to print the res.status error code? That said... When this situation is going on, the client grinds to a halt, and lockd seems "stuck" in D state. I tried killing or stracing it, to try to clear the error, before I found out it is a kernel deamon... When this failure happens, I get the impression that lockd keeps on trying to be "of service", retrying operations that are bound to fail. So maybe the error should be cached, and then immediately handled instead of making the client grind to a halt. (it is the (one second?) timeout in nsm_mon_unmon and the big backlog of requests that result in the same call and timeout that frustrate the client... ) Roger. -- ** R.E.Wolff@xxxxxxxxxxxx ** https://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** f equals m times a. When your f is steady, and your m is going down your a is going up. -- Chris Hadfield about flying up the space shuttle.
