We just had an example of a run away process with one of our authenticated users. I would have liked to kill off the user's processing while leaving all the other users running. Any ideas as to how to accomplish this? I do know the user's login and password, but little else. We use the Cookie Crumbler and a slightly hacked UserFolder for authentication. --
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dennis Allison wrote:
We just had an example of a run away process with one of our authenticated users.
I would have liked to kill off the user's processing while leaving all the other users running.
Any ideas as to how to accomplish this? I do know the user's login and password, but little else. We use the Cookie Crumbler and a slightly hacked UserFolder for authentication.
Can't be done. There is no safe way to interrupt an in-process request, even if you could figure out that it "belonged" to a given user; any attempt will likely leave your system hosed, requiring an appserver restart. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDkkUt+gerLs4ltQ4RArxqAKCo+bU+KoO0fGslDrttCUfGeIBAigCfZjlM gg2zJZMjICst+ECc23xfELk= =EkrC -----END PGP SIGNATURE-----
Dennis Allison wrote:
We just had an example of a run away process with one of our authenticated users.
What do you mean by this? If it's something to do with a relational database, you might be able to do something there...
I would have liked to kill off the user's processing while leaving all the other users running.
As Tres pointed out, can't really be done. Restarting Zope will do it... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (3)
-
Chris Withers -
Dennis Allison -
Tres Seaver