Hi John,
On Dec 29, 2008, at 9:50 AM, Simon John wrote:
> Hi,
>
> I'm writing some NASL plugins at the moment and am getting fed up of
> going through the following procedure to make sure the new script is
> seen by NessusClient:
>
> 1. copy script from Git repository to the plugins directory
> 2. sign the script with nasl -S
> 3. nessusd -R
> 4. /etc/init.d/nessusd restart
> 5. reconnect client to server
>
> The worst part is nessusd -R which takes forever even on a 3.2GHz quad
> core! Isn't there a way this can be skipped or sped up as its a bit
> of a
> pain, especially when you've forgotten a semi-colon somewhere in your
> script and you've got to go through it all again!
>
> I can only think of temporarily moving most of the plugins out of the
> way, just leaving enough to satisfy dependencies.
>
> Any other ideas?
nessusd -R purges the entire plugin database and re-processes every
plugin. This should only be used when a DB is corrupt.
For your use case, you should use nessusd -t which performs a checksum
on each plugin and only reprocesses those which changed. It's way
faster and should remove the pain.
Also, prior to putting the script into the plugins/ directory, you
should use nasl -L to make sure it parses properly.
-- Renaud
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
