-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seperate from general cronjob #20
Comments
At a quick glance, I have no idea how to make a separate cronjob run only 1 event, on a different schedule, much less a newely created event that has nothing to do with the daily crontjob event. |
I have an idea. I have created a command, a compatible event, but I don't know hot to submit that event. |
i probably do not know, but if you can show me where you are going, i might be able to think about it more. |
We have now our own cron job. You can simply run
from your crontab, beside your usual cronjob command. In case you have too many actions to fix: UPDATE actions SET event_name = 'mailmagik.fetchmail' WHERE event_name = 'task.cronjob.daily'
AND action_name LIKE '%ConvertEmailTo%' Of course, fully at your own risk. |
wow look at that, good stuff. goes way over my head! |
Yeah, learning about the event system was not easy. |
Cool.. Thanks for this update
hoping this update will solve the issue. Will test out and will report if I find any issues. |
i just tested and it works flawlessly. this is my new crontab file:
|
Does this resolve the previous problem of at least a task in a project required to initate the email fetch ? if so the readme can be updated with the same |
it appears so! |
Let me explain a problem I encounterd .
The general cron job also used to sent out reminders for tasks that are due , so we could set only daily schdule for it.
But for taks generation through email , should be somthing to be executed at least hourly.
So putting both jobs in same cron will flood up the email inbox if you have enabled the email notifications.
Originally posted by @isvfgs in #16 (comment)
The text was updated successfully, but these errors were encountered: