Ok, further problems
I've got it set for 2 (which was the original run time from the 
scheduled tasks) and I'm still getting multiple reports. They are 
definately seperate run events too.
For examples:
Saturday I received 5 RebuildSpamDB - report emails between 2:25-2:44 am 
local
Each had a different started line

RebuildSpamDB 2.7.1.6 (1.0.02) started - Sat May 22 02:19:27 2010
RebuildSpamDB 2.7.1.6 (1.0.02) started - Sat May 22 02:24:22 2010
RebuildSpamDB 2.7.1.6 (1.0.02) started - Sat May 22 02:29:25 2010
RebuildSpamDB 2.7.1.6 (1.0.02) started - Sat May 22 02:34:22 2010
RebuildSpamDB 2.7.1.6 (1.0.02) started - Sat May 22 02:39:26 2010


Each seems to go through the entire script, but still seems weird
I've moved the rebuild back over to a scheduled task on windows, unless 
someone says it's fixed or asks for some further information

Just kibitzing, but it seems like the part that would select the time to 
run is randomized between hour and hour+1, ie: the first time my script 
ran was randomly selected at 2:19a
When the script runs, it selects the next run time, ideally for the next 
day (ie: my next run time should've been Sunday the 23rd at 2:24a) but 
something isn't forcing it to wait till the next day and it sees 2:24a 
as the next run time.
If this is correct, I'd suggest a "wait flag" that doesn't let it chose 
the next time until hour+1 arrives (ie: my setting is at 2, so it picks 
something between 2 and 3, the wait flag would be set to 3 and once 3 
comes, the next runtime would be randomly picked between 2 and 3. Not 
sure if this would work well where a user has selected side-by-side 
hours of runtime (ie: runtimes 1|2|3|4|5|6|7...etc)

On 5/20/2010 7:43 AM, Fritz Borgstedt wrote:
> [email protected] schreibt:
>    
>> It's not killing anything to have the script run twice, but it is
>> unusual and thought I'd point it out
>> If there's a suggestion that it's a setting I have that needs to be
>> fixed, I'm happy to check
>>      
> set the schedule to 1.
> I will disable the "24" option, too much hassle with the rollovers at
> that time.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Assp-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-user
>    


------------------------------------------------------------------------------

_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to