On 2005.06.29, Thorpe Mayes <[EMAIL PROTECTED]> wrote:
> Just this week ns_schedule has started to behave oddly. Instead of
> running the code one time, as it has for months on end, it now runs the
> code twice.

Connect to the control port (assuming you have nscp set up - if not, go
set it up) and do "join [ns_info scheduled] \n" and see if you see your
proc scheduled twice.

If it is scheduled twice, then you need to try and figure out if/why it
is.  Perhaps stick an ns_log statement inside the if-block and see if it
gets logged twice.  If it doesn't get logged twice, then you have code
somewhere else that's also scheduling the proc.

-- Dossy


> ns_share daily_okiechef_sweep_scheduled_p
> if { ![info exists daily_okiechef_sweep_scheduled_p] } {
>     ns_schedule_daily -thread 2 0 daily_okiechef_sweep
>     set daily_okiechef_sweep_scheduled_p 1
>
> #    set x [ns_schedule_daily -thread 2 0 daily_okiechef_sweep]
> #    ns_unschedule_proc $x
> }


--
Dossy Shiobara                       mail: [EMAIL PROTECTED]
Panoptic Computer Network             web: http://www.panoptic.com/
  "He realized the fastest way to change is to laugh at your own
    folly -- then you can let go and quickly move on." (p. 70)


--
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.

Reply via email to