egghelp/eggheads community

bind time

2003-12-08T15:46:26-04:00

1st code is not correct, it doesn't work like that.
but the second code is correct, it will trigger myProc every 5 mins.

read tcl-commands.doc.

Statistics: Posted by Sir_Fz — Mon Dec 08, 2003 3:46 pm

bind time

2003-12-08T15:24:07-04:00

i actually have a related question...

i'd like to use a bind time to trigger something to run every five minutes (i want to make sure it executes at :00 :05 :10, etc)... how do i do this? can you comma-separate multiple values like you can with crontab, or do i have to set up two binds?

crontab-style:

Code:

bind time - "?0,?5 *" myProc

two timers:

Code:

bind time - "?0 *" myProcbind time - "?5 *" myProc

thanks, as always, for any help

Statistics: Posted by LtPhil — Mon Dec 08, 2003 3:24 pm

bind time

2003-12-03T09:09:53-04:00

/me's just trying to pick a fight as always

ok, lets take this one outside *maybe closed*

Statistics: Posted by GodOfSuicide — Wed Dec 03, 2003 9:09 am

bind time

2003-12-02T20:42:16-04:00

If you want an interval that large, it's usually a number of hours/days. (change the bind/calculation) His request was for 90 minutes though.
I like the idea of just having to unbind to stop it and the fact that it's running "in sync" with the time. (so you can predict when the proc will run your code without having to know when the script was started/start it at a particular time.)

He might not want that though

On the downside, the code matching the masks for a time bind doesn't handle timer drifts very well (iirc), so you might get a few skipped runs if the box you're running it on is REALLY busy around the time your bind mask matches.

/me's just trying to pick a fight as always

Statistics: Posted by user — Tue Dec 02, 2003 8:42 pm

bind time

2003-12-02T19:20:25-04:00

The code doing the check for an existing timer is much more cpu intensive than my time calculation

the call for [timers] is only triggered when the actual proc is hit, it's used to avoid double timers when doing a rehash / whatever.

if the intervall would be 10000000 (or something large) your code would check a few hundret times it the exact has been reached (either that or i'm too drunk to understand the code again).

Statistics: Posted by GodOfSuicide — Tue Dec 02, 2003 7:20 pm

bind time

2003-12-02T14:46:34-04:00

user: i think the direct timer works a little better

In what way? The code doing the check for an existing timer is much more cpu intensive than my time calculation and the eggdrop code dealing with timers / bind time is pretty much the same (iirc)

Statistics: Posted by user — Tue Dec 02, 2003 2:46 pm

bind time

2003-12-02T10:36:53-04:00

user: i think the direct timer works a little better

Statistics: Posted by GodOfSuicide — Tue Dec 02, 2003 10:36 am

Workaround for the "limits" to bind time

2003-12-02T09:33:40-04:00

Code:

# interval in minutes# (you could of course hard code the interval value into the# proc if you don't need it to be easy to spot and change :)set interval 90# this bind will trigger the proc every ten minutes# (whenever the last digit of the minutes is "0")bind time - ?0* timedThingproc timedThing args {# this calculation makes sure the code is only executed# at the given intervalif {![expr {([clock sec]/60)%$::interval}]} {# insert your code here}}

PS: since the proc is only triggered every ten minutes, make sure your interval value matches that (ends with a 0). If you need a finer "resolution", change the bind. (* as a mask for every minute)

Statistics: Posted by user — Tue Dec 02, 2003 9:33 am

bind time

2003-12-01T16:06:58-04:00

yeah, got that Thanx for the info.

Statistics: Posted by Sir_Fz — Mon Dec 01, 2003 4:06 pm

bind time

2003-12-01T13:53:27-04:00

edit: sorry... guess i'm too ill to think today.

Statistics: Posted by arcane — Mon Dec 01, 2003 1:53 pm

bind time

2003-12-01T12:59:32-04:00

If I understand well, what you mean is that there can't be 90 mins in a clock (since 1 hour = 60mins) well if that's how bind time functions

bind time is for exact values.

bind time 00 ** ** ** ** (or even 00 *) would trigger every full hour (00:00, 01:00, 02:00, etc)
bind time ?0 ** ** ** ** (or even ?0 *) would trigger all 10 minutes (00:00, 00:10, 00:20, etc)

Statistics: Posted by GodOfSuicide — Mon Dec 01, 2003 12:59 pm

bind time

2003-11-30T18:42:36-04:00

[snip]
bind time works with
your bind would trigger every hour that has the minute value of 90...this aint gonna happen i'd say.
[snip]

If I understand well, what you mean is that there can't be 90 mins in a clock (since 1 hour = 60mins) well if that's how bind time functions (because I don't exactly know how bind time functions) then my bind is wrong, else its correct.

Statistics: Posted by Sir_Fz — Sun Nov 30, 2003 6:42 pm

bind time

2003-11-30T18:05:16-04:00

this will trigger proc every 90 minutes.

are you sure ? either i'm drunk or this proc will never be triggerd.

bind time works with
your bind would trigger every hour that has the minute value of 90...this aint gonna happen i'd say.

Code:

proc someproc {args} {        foreach i [timers] {         if {[lindex $i 1] == "someproc"} {             killtimer [lindex $i 2]         }        }       putlog "TRIGGERD ALL 90 MINS"       timer 90 someproc}timer 90 someproc

Statistics: Posted by GodOfSuicide — Sun Nov 30, 2003 6:05 pm

bind time

2003-11-30T15:30:15-04:00

Thanks

Statistics: Posted by Jag — Sun Nov 30, 2003 3:30 pm

bind time

2003-11-30T14:40:43-04:00

Code:

bind time - "90 *" proc

this will trigger proc every 90 minutes.

Statistics: Posted by Sir_Fz — Sun Nov 30, 2003 2:40 pm