[Openvas-devel] Concurrent hosts and tests options
felix.wolfsteller at intevation.de
Wed Sep 2 08:35:08 CEST 2009
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).
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 Galitz
> Blankenheim NRW, Germany
> > -----Original Message-----
> > From: openvas-devel-bounces at wald.intevation.org [mailto:openvas-devel-
> > bounces at wald.intevation.org] On Behalf Of Thomas Reinke
> > Sent: Dienstag, 1. September 2009 23:14
> > To: openvas-devel at 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 at wald.intevation.org
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
More information about the Openvas-devel