You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! It seems that I ran into the opposite of #154. I use cron in the program that starts shell scripts on a schedule. Sometimes the program remains in the background and I close the laptop. Several hours later, after the night, the laptop is waked up and the CPU is overloaded because thousands of shell scripts are started %)
The system is Ubuntu 16.04 and the code is like this:
initialization code:
entryId, _ := sm.cron.AddFunc(newEntry.Crontab, func() {
logEntry.Debugf("fire schedule event for entry '%s'", newEntry.Crontab)
ScheduleCh <- newEntry.Crontab
})
go routine:
select {
case ev := <-ScheduleCh:
scripts[ev.Crontab].Start()
...
}
Do you have any idea why cron can execute the callback multiple times after time changes?
The text was updated successfully, but these errors were encountered:
Hello! It seems that I ran into the opposite of #154. I use cron in the program that starts shell scripts on a schedule. Sometimes the program remains in the background and I close the laptop. Several hours later, after the night, the laptop is waked up and the CPU is overloaded because thousands of shell scripts are started %)
The system is Ubuntu 16.04 and the code is like this:
Do you have any idea why cron can execute the callback multiple times after time changes?
The text was updated successfully, but these errors were encountered: