Outcome is: you should have maximally (#maxhost * #maxchecks) processes that run NVTs at the same time (per scan) + 1 openvasd "main" process + 1 openvasd process per scan serving the client and doing scheduling etc. Note though that there are some hardcoded limits (20 for checks I think).
-- felix On Tuesday 01 September 2009 23:26:02 Geoff Galitz wrote: > Thanks Thomas. That was my understanding, but I needed to verify that for > my current project. > > -geoff > > > --------------------------------- > Geoff Galitz > Blankenheim NRW, Germany > http://www.galitz.org/ > http://german-way.com/blog/ > > > -----Original Message----- > > From: openvas-devel-boun...@wald.intevation.org [mailto:openvas-devel- > > boun...@wald.intevation.org] On Behalf Of Thomas Reinke > > Sent: Dienstag, 1. September 2009 23:14 > > To: openvas-devel@wald.intevation.org > > Subject: Re: [Openvas-devel] Concurrent hosts and tests options > > > > A. Concurrent hosts - the # of hosts that are simultaneously tested. > > B. Concurrent tests - the # of tests (per host) that may be > > simultaneously run. > > > > If you launch a test against two machines (e.g. 192.168.1.1,192.168.1.2) > > you will start auditing both IPs simultaneously if and only if > > concurrent hosts is > 1. Within each IP being tested up to "B" > > concurrent tests will be run simultaneously, at most, providing > > plugin scheduling and dependencies allows for it. > > ... > > _______________________________________________ > Openvas-devel mailing list > Openvas-devel@wald.intevation.org > http://lists.wald.intevation.org/mailman/listinfo/openvas-devel -- Felix Wolfsteller | ++49-541-335 08 3451 | http://www.intevation.de/ PGP Key: 39DE0100 Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel