Setclientid / Definition of client

[Felix Engel]

On Mon, Dec 04, 2006 at 01:31:35PM -0500, J. Bruce Fields wrote:
> On Mon, Dec 04, 2006 at 01:11:45PM -0500, Trond Myklebust wrote:
> > Our client will always try a RENEW first. If that fails, then we
> > setclientid,
> 
> and the same if the RENEW fails because your credentials expired?
> 
> > if that fails, we change the client identifier string.
> 
> OK.  Well, I can fix the server to allow it to remove unused client
> state earlier, and that'll fix the reported symptom--the server won't
> complain about setclientid's with bad credentials any more--but falling
> back on a differen client identifier should work in that case, so I
> still don't understand the originally reported problem.

Sorry, it seems I wasn't very clear in my first posting. The complete
lockup was indeed a problem with the 2.6.17 used in the FC4
installations. That doesn't happen with 2.6.19, where, as Trond
described, the identifier string is changed. 

However that effect happens quite often (about every 20 minutes), and
causes lots of error messages in the server's kernel log. Since the RFC
stated that the identifier string should be constant across reboots we
were also wondering that it is changed so easily.

Anyways, the discussion here is very helpful, so thanks for your time.
I will be following further, so if you need more detailed information,
please let me know.

Regards, Felix