On Thursday 11 March 2010 20:48:25 mer...@gmx.net wrote:
> My meaning to this good idea.
> Sceduled tasks are fine like it is always implemented (parallel scans -
> tasks). Pausing them needs to syncronize thats not be a trivial
> implementation.
>
> Lets explain.
>
> The scan starts and paused, so plugins are used can updated in the pausing
> period. So the information is not the correct one (maybe). Only used plugins
> need a syncronize mechanism. So why pausing a scan, if there is the
> possebility to manage scans as timed scans ?
Apart from the fact that changing NVTs happen rarely, this race
condition is present already now.
> Did not see the advantage of that.
Well, the tremendous adavantage is that we can pause the scan activity.
This is important from a scan management point of view.
Best
Jan
--
Dr. Jan-Oliver Wagner | ++49-541-335084-0 | http://www.greenbone.net/
Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück
AG Osnabrück, HR B 202460 | Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver
Wagner
_______________________________________________
Openvas-devel mailing list
Openvas-devel@wald.intevation.org
http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
