I set up my events for echomail polling according to the instructions
from MysticGuy's 5-year-old videos.
In the video, he says that using the settings he suggests will poll
every hour on the 5 minute mark...
However, my system is polling every 5 minutes -- WAAAAAAY too often.
There isn't a good description or hint available as to what these fields actually mean. If I set "hour" to "1," does that mean run every hour
(and then 2 would mean every 2 hours) or does it mean run at 1AM?
There isn't a good description or hint available as to what these fields actually mean. If I set "hour" to "1," does that mean run every hour
(and then 2 would mean every 2 hours) or does it mean run at 1AM?
If I want to run an event on the 27th minute of every hour, for example, would I set hour to "1" and "minute" to 27?
It's also worth noting that MIS needs to be restarted for event changes
to take effect.
For non-Interval and non-Semaphore events to fire on a certain minute every hour, I believe you would have to create 24 events (one for each hour), and specify the desired hour (Exec Hour) and minute (Exec Min)
for each of them.
I think that may be why I've been so frustrated with my...um...current events...problem! I had assumed that any changes to events were instant.
semaphore). For 'Interval' events, this applies for sure, which is why 'Hourly' events were created...
I've also tried to change the starting time of a shell event forward for testing purposes, but it appeared to keep track of that the event had already fired that day, and refused to run it again that day, which
caused me quite a bit of confusion... :-D
But, do the Hourly events allow you to specify the exact minute on which they should be run every hour?
As I understand it, the 'hour' field is ignored when the event type is
set to 'Hourly' or 'Semaphore'. It is definitely used as a 1-24
reference to a specific hour, when the event type is 'Shell' or 'Interval', because my weekly maintenance event happens at a specific
time on a specific day.
But, do the Hourly events allow you to specify the exact minute on which they should be run every hour?
That was the clue I needed. My mail poll was set to interval, so having "minute" set to 5 meant "5 minute interval." Changed it to "hourly" and we shall see.
But, do the Hourly events allow you to specify the exact minute on wh they should be run every hour?
I think I have a solution for this for Linux users -- and I'm sure you coul set it up with task scheduler.
Set up a semaphore event for anything you want to trigger that
precisely, then use cron to "touch" the semaphore file.
Yes, that probably will fix things. But I need to stress the difference between 'Hourly' and 'Semaphore' here: make sure you have both! (o_O)
Let ./mis (and ./mutil) take care of Mystic. Don't ask the end user's OS to do it instead. That's a bad habit that programmers should avoid. I would pretend to know.
Yes, that probably will fix things. But I need to stress the differen between 'Hourly' and 'Semaphore' here: make sure you have both! (o_O)
I have an hourly "poll regardless" and a semaphone "poll when I have something to go out" and a semaphore to unpack inbound in case of a crashmail.
Let ./mis (and ./mutil) take care of Mystic. Don't ask the end user's to do it instead. That's a bad habit that programmers should avoid. I would pretend to know.
If Mystic gave me that option, I wouldn't use a workaround. But if (for some reason) I need to run things with control levels that Mystic
doesn't allow, then you could use cron (or any other tool that you want
to use to force mystic to execute an event via semaphore)
From my experience, yes...That's exactly what 'Exec Min' does.
Currently, I have two 'Hourly' events, one to poll fsxNet, and another
to poll Fidonet. The fsxNet event is set for :00 because fsxNet is
simply better, and the Fidonet poll is set at :05 because it deserves to wait another five minutes. (o_-)
But, do the Hourly events allow you to specify the exact minute on wh they should be run every hour?
I think I have a solution for this for Linux users -- and I'm sure you coul set it up with task scheduler.
Set up a semaphore event for anything you want to trigger that
precisely, then use cron to "touch" the semaphore file.
| Sysop: | Gary Ailes |
|---|---|
| Location: | Pittsburgh, PA |
| Users: | 132 |
| Nodes: | 5 (0 / 5) |
| Uptime: | 108:54:27 |
| Calls: | 733 |
| Files: | 2,171 |
| Messages: | 81,483 |