Hi, the configuration looks OK ... what the problem is? (please provide the error messages or describe the expected behaviour vs. reality).
If you use the "every <x> cycles" option, the cycle length is set with the global "set daemon <y>" => if you want to run it once per 15 minutes, with that configuration the "set daemon 60" should approximately do the trick. Note that monit scheduler currently isn't wall-clock based ... the cycle length is variable (based on number of tests and timeouts ... the "set daemon" sets the sleep interval between cycles => even with 15 * 60 it won't be exactly 15 minutes as the time consumed by the cycle itself is not included. We will fix this in the future - the monit scheduler will allow the run the tests at exact time. Regards, Martin On Dec 18, 2012, at 5:28 PM, Christina Arsenault <[email protected]> wrote: > Hello Everyone, > > > > I am trying to kick off a python script to run once every 15 minutes and to > timeout if it takes more than 60 seconds to run. I think maybe I'm doing the > wrong kind of "check", here is my attempt. > > check program movie_creation with path "/usr/bin/python > /home/carsenault/hlcam/videos/monit_movie_creation_test.py" with timeout 60 > seconds every 15 cycles > if status != 0 then alert > > > Thanks in advance for your help! > > Christina Arsenault > > > -- > To unsubscribe: > https://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
