On Mon, 2005-10-17 at 11:45 -0400, Richard F. Rebel wrote:
> DBG is an already open auto-flushed file handle. The AuthzHandler
> prints to it, other invocations of cleanup handler print to it, and only
> when user presses stop do we not ever the output from this line.
I suggest you print to STDER
On Mon, 2005-10-17 at 11:31 -0400, Perrin Harkins wrote:
> It sounds like you're jumping to conclusions to me. The cleanup handler
> does execute, even when the user presses stop, unless something
> catastrophic is happening like an actual segfault.
>
> My guess would be that something is going
On Mon, 2005-10-17 at 11:16 -0400, Richard F. Rebel wrote:
> When a user starts a program which takes a few seconds to run, and you
> hit the stop button, then start another, the user is denied, which is
> correct behavior. The problem is that the lock is never removed as the
> cleanup handler nev
Maybe some more information would be useful here.
We have a couple hundred old reporting CGI's. We have a bunch of users
whom sometimes think they run too slow so either it the stop button on
the browser, or they are the type to double click on buttons or links
causing multiple copies to run.
T
On Fri, 2005-10-14 at 17:32 -0400, Richard F. Rebel wrote:
> I have been noticing that PerlCleanupHandlers are not called when a user
> pressed the STOP button in their browser before the page is downloded.
Yes it is, but not until the request is actually completed. If you want
to stop your handl
Hello,
I have been noticing that PerlCleanupHandlers are not called when a user
pressed the STOP button in their browser before the page is downloded.
Is this normal behavior or a bug?
I really need my handler to run no matter what if possible, at the end
of the cycle. Is there a way to achiev
