It's probably a hardware problem, but not the issue with the Nessus or the scripts you use.
> A different web interface will not help in this case which > occured because the config file could not be read properly. > > I already have the functionality to disable new plugins as > they're downloaded but this doesn't help this situation :-( > > > Currently Nessus enables any new plugins that are not > > mentioned explicitly by number in the config file. Is there a > > way to disable this?
