Forum OpenACS Development: Re: Schedule a procedure to run on 1st of every month in project open.

The technical part is not complicated, I believe the primary issues are in how your trial solution is designed and in how it is factored. As mentioned above, you need to factor such that the function you call is not dependent on the time. If you refactor in this way, you will (1) be able to call it from a link and (2) will also be able to schedule it, or wrap it in a scheduler which may have been defined by project/open or that you might define.

In https://openacs.org/forums/message-view?message_id=3438041 you say:

I dont need any filter by time functionality.
Good point. I agree, you do not need such filtering. But, in https://openacs.org/forums/message-view?message_id=3437903 you say:
Calling the proc in my link target will not help because the proc has a condition that it will run only on 1st of every month.
So I have one question about that. Why do you have this filtering functionality you know you don't need?

You use bind, but bind is associated with events from the X window system, something you don't use (I am given to understand from your writings that you use ms windows); from the man page for bind:

NAME
bind - Arrange for X events to invoke Tcl scripts

You posted this...

proc time:proc { min hour day month year } {
...
}

is this the proc you wish to run? or, do you want to create a proc that schedules a proc of constant name?

When and under what conditions do you intend to run time:proc? What is it meant to do?

Please make it easy to understand your intent; trying to guess is a useless waste of time. It's evident your full intent is not completely explained since you're asking more questions and changing the requirements in mid-query.

I happen to hold the opinion that we can create something that will work, and to the extent you're willing to cooperate in asking for help, I'm willing to supply some help to you as long as that fits within my schedule. Please don't forget we're volunteering to help (for example, we are NOT paid support for project/open). Your cooperation is requested as we all notice that all of us, yourself, myself and everyone listening to this deserves respect for their time.

I would like to let you know about ad_proc; you can look that up in the api browser.

Hey Jim,

The "bind time" itself acts as a scheduler. Inside the time:proc(just a proc name, which is scheduled by the bind) we need to mention our procedure which need to be scheduled. Madhavi has already mentioned in her first post about calling the time:proc by the

bind time - "00 00 01 * *" time:proc

As you said about the ad_proc, I agree with that. Here the issue is "bind time" thing is not supported in Project Open. So Madhavi is requiring an alternative to that.
As far as Madhavi's issue is concerned, may be the "cronjob" package is the remedy for that. I suggest to try that.

Cheers..

-IQBAL

Heya IQBAL...

Just a look at how the wind is presently blowing... I've checked with tcl devs, they say support for tcl-8.4 is hanging by a thread, so you might test p/o with aolserver-4.5.x and tcl-8.5; the tcl folks are saying that there are fewer bugs, more support and an interesting little list feature that's kinda like an iterated shell backquote, turns a list appearing as a single parameter, into each item of the list as a parameter.

I know oct is aware of this, and they made some decisions about future openacses; check with them to see what they decided about tcl.

Before there are too much rumors in this thread:

Concerning the "bind" command floating around in this thread: If you are talking about the "bind" from the tcl/tk manuals, the discussion is pointless, since "bind" is a tk command, not available in tcl only apps (such as aolserver) and not particulary useful for the discussed functionality either. i can't exclude that there is a tcl proc named "bind" provided by ]po[.

Concerning Tcl 8.4 and 8.5: I fail to see any connection to this topic. However the sitation is as follows: The Tcl Core Team wrote more than two years ago: "Routine maintenance of Tcl/Tk 8.4 has now come to an end". So, OCT decided to switch to Tcl 8.5:
http://www.openacs.org/forums/message-view?message_id=3357449