-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/05/2009 04:55 PM, Simo Sorce wrote: > On Mon, 2009-10-05 at 15:58 -0400, Simo Sorce wrote: >>> Consider the case where our backend crashes and is restarted by the >>> monitor. If we have a busy system where one entry is being requested >>> continuously, say once per second, and the backend that NSS is >> talking >>> to segfaults for some reason, that request would never get a reply, >> and >>> the timeout would continue to be extended. Furthermore, all new >> requests >>> would just continue to add to the queue of callbacks, never to see >> the >>> light of day. >>> >>> No, it's much better to just let the first timeout cause all of them >> to >>> return immediately, so that a new request can try again. >> >> Yeah hadn't thought about it from this pov. >> >> Will remove the extending timeout part. > > New revision attached. > > Simo. > > > ------------------------------------------------------------------------ > > _______________________________________________ > sssd-devel mailing list > sssd-devel@lists.fedorahosted.org > https://fedorahosted.org/mailman/listinfo/sssd-devel
Ack. - -- Stephen Gallagher RHCE 804006346421761 Looking to carve out IT costs? www.redhat.com/carveoutcosts/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkrKYa4ACgkQeiVVYja6o6PGtgCbBa/oFMA62uqDB4TV0va/envr /dgAnj085yU70lXfDxncKZZhTaycAW6W =/1Mw -----END PGP SIGNATURE----- _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/sssd-devel