I believe ns_ictl is what you would want - "ns_ictl oncleanup" I believe.
Another option is to run all request through a configured "start page" and to put the cleanup code in that .adp page. Nice thing about that approach is that you can make changes without having to restart the server. Configuration: ns_section "ns/server/server1/adp" ns_param startpage <PATH>/start.adp start.adp: <% _ns_adp_include [ns_url2file [ns_conn url]] # # tDOM cleanup code goes here. # %> On 2/28/07, Tom Jackson <[EMAIL PROTECTED]> wrote:
Yes, wouldn't it be nice if ns_atclose worked in scheduled procs? In a conn you can use ns_atclose, but it has been removed from scheduled procs. Is there no way to run a trace on a scheduled proc? I have looked at ns_ictl, but it looks like the scheduling is per module, so you can't just activate it when you want like ns_atclose. Not having to catch code is a big benefit, being able to use the same code in all threads would be very nice. tom jackson On Wednesday 28 February 2007 11:41, Nathan Folkman wrote: > Don't you open yourself up for a race condition if that code is in a > scheduled proc? -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to < [EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
-- Nathan Folkman [EMAIL PROTECTED] -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
