> -----Original Message----- > In addition, nessusd forks to service each client connection. Each > child thread holds a a snapshot of the plugins that parent knew about > when it was created and is is unaffected by the HUP signal sent by > nessus-update-plugins. This means that a currently running scan will > not know about plugins added once it starts.
Sounds good so far. Will the running scan use updated plugins that it already knew about when it started. ie if the same plugin existed before the scan started, but was updated after the scan started but before it had run that plugin, which plugin would run the old one or the updated one? What about when a plugin is removed. What happens then to the running scan if a plugin it knows about is removed before it gets to it? Thanks, George --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.788 / Virus Database: 533 - Release Date: 11/1/2004 _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
