I can't reproduce it by simply setting a channel to overdue, plucking it,
and checking the new schedule date. That seems to work fine.
I am starting to wonder if it is related to leaving my machine running 24
hours a day. I don't leave Plucker desktop running, but the machine often
doesn't get shutdown - I just lock it when I leave, so I can dial into it.
I will turn off the machine each night for a few, to see if the same thing
happens.
"Robert O'Connor"
<[EMAIL PROTECTED]> To:
[EMAIL PROTECTED]
Sent by: cc:
plucker-list-admin@rubberc Subject: Re: Plucker
scheduler problem
hicken.org
25/09/2002 09:02 AM
Please respond to
plucker-list
On 24 Sep 2002 at 16:03, Fringe Ryder wrote:
> At 08:34 AM 9/25/2002 +1000, [EMAIL PROTECTED] wrote:
> >Example: Say, I have a 'pluck' scheduled for 7 am in the morning each
day,
> >but I have it set to only do the plucking on demand. When I get to
work
> >at 8am, I tell it to go get the channel. When it finishes it seems to
set
> >the next due date, not for 7 am the next morning, but for 7am the day
after
> >that.
> >
> >Has anyone else noticed this?
>
> I noticed that too, but figured I was screwing something up.
I can't seem to reproduce this--AFAIK it is working for expected for me.
Can you give a blow by
blow steps to reproduce?
IIRC code goes like this (using 1 day interval as your example):
Add one interval onto update_base time. Is the new_update base past "now"?
If not, add another
interval, and so on until it is.
Best wishes,
Robert
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
