Good point there. The part i don’t understand is why he is using a machine with
considerable resources to run the manager which isn’t the most resource
intensive process of OpenVAS.
To used that hardware properly virtualization to have one Manager in one VM and
a Scanner in another VM would be
to make it more clear for people who think "my single process has to
utilize my hardware":
you won't get far when you complain why your webserver does not utilize
your CPU and memory as much as you like it because it spends most of the
time by wait for the overloaded database-server which can
In my opinion i think that those resources would be better spent on openvassd
process since it does the heavy lifting.
Fabio
> No dia 08/01/2017, às 00:59, Reindl Harald escreveu:
>
>
>
> Am 08.01.2017 um 01:30 schrieb TN TN:
>> HI Christian, I actually have it
Am 08.01.2017 um 01:30 schrieb TN TN:
HI Christian, I actually have it installed with postgresql, but when
you're scanning thousands of internal hosts on a weekly basis it slows
it down considerably over time.. I'm just curious on why openvasmd is
not using enough resources on the server.
HI Christian, I actually have it installed with postgresql, but when you're
scanning thousands of internal hosts on a weekly basis it slows it down
considerably over time.. I'm just curious on why openvasmd is not using
enough resources on the server. Thanks TN
On 7 January 2017 at 17:09,
Hi, I have a fairly powerful server and it seems like the openvasmd process
isnt using up alot of the resources on the box. If I run numerous scans
(the scanner being off of the main openvasmd server), the openvasmd process
barely uses any resources, however Greenbone slows down and the backend