Not to my knowledge and it's quite annoying. I have 1 master and 2 slaves running the jobs and I completely gave up on scheduling with OpenVAS. Why care about which day/hour it starts and why limit it to a specific amount of runtime, hell if I know how long something will take. Currently I am using / developing my own bash script which calls and parses omp to schedule a maximum of 2 jobs per slave; any job that hasn't run the current month. I haven't worked it out nicely enough to release it or perhaps rewrite it in python but it's doing wonders to just let things work for me.
Kind regards / Vriendelijke groet, Internedservices Thijs Stuurman Security Specialist Thijs Stuurman Wielingenstraat 8 | T +31 (0)299 476 185 1441 ZR Purmerend | F +31 (0)299 476 288 https://www.internedservices.nl | KvK Hoorn 36049256 Internedservices is ISO 9001:2008, ISO/IEC 27001:2005, ISO 20000-1:2005, NEN 7510, ISAE 3402 en PCI DSS certified. -----Oorspronkelijk bericht----- Van: Openvas-discuss [mailto:openvas-discuss-boun...@wald.intevation.org] Namens Bryan Brannigan Verzonden: Monday, January 9, 2017 7:15 PM Aan: openvas-discuss@wald.intevation.org Onderwerp: [Openvas-discuss] Restrict concurrent tasks Is it possible to restrict the number of concurrent tasks started? I have 22 tasks scheduled to start at the same time, but can really only handle 5 concurrently. I'm trying to avoid rolling schedules if possible. _______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss _______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
