KS says:
Hi,KS-Soft wrote:We have such task in "to do" list. It has low priority because we think most users do not need such option.
If we are wrong, please post your opinion into "Wish list" forum. Use this forum what something does not work.
Regards
Alex
for instance when testing if a cron job ran successfully one needs tests to have ran at a defined time, like a cron job in *nix or "at" in Windows. The procedure KS advises is very unpracticable.
It is really a pain to define such schedules for timetables that could be so easy. Whereas it might work that way it is inconvinient and illogical and therefor error prone to define a test running each full hour with hundreds of clicks and entries.
How would I fine tune a test that runs each full hour ? 0 * * * * run test took 16x24 (= 384!!!!) settings going the KS-way.
How would I fine tune a test that runs 00/10/20/30/40/50 per hour? 0,10,20,0,40,50 * * * * run test took 6x16x24 (= 2304!!!!) settings going the KS-way.
Just to define ONE single schedule!
*nix provides a well-tried way to define such absolute schedules and I wanted the same in HostMon.
Thank you, Rainer