Michael, I always thought the order is maintained for these 3 categories,
ACT_INIT ACT_SCANNER ACT_SETTINGS If this launch order is maintained, NVT authors need not, for example include find_service.nasl in all NVTs that need service detection or port status. If NVTs in the above category rely on another NVT in script_dependencies which is an ACT_GATHER_INFO or something else, it'll automatically launch that. But, the scheduler should always try to launch any NVT that is in those 3 categories first. Thanks, Chandra. -----Original Message----- From: Openvas-devel [mailto:openvas-devel-boun...@wald.intevation.org] On Behalf Of Michael Wiegand Sent: Tuesday, September 18, 2012 3:06 PM To: openvas-devel@wald.intevation.org Subject: Re: [Openvas-devel] Sequencing of scripts - dependency ordering messed up? Hello, As far as I can tell from a quick glance at the code Felix is correct, the pluginscheduler does not care about categories (ACT_*) when scheduling. I guess this is the result of a decision in pre-OpenVAS times that dependencies have a greater priority than categories. Apart from Thomas mail I have not heard of this causing problems, so I would be interested in a reproducible scenario for this. As Felix said, deciding between dependencies and categories is not simple, I could see both choices having their advantages and drawbacks, but I also interested in opinions on this, especially from the NVT developers perspective. Regards, Michael * Felix Wolfsteller [13. Sep 2012]: > Iirc, years ago following was true (and I doubt it changed): > Dependencies can mess the "Phases" up. If a ACT_SCANNER would depend > on something from ACT_DENIAL, the ACT_DENIAL one would go first. > The whole dependency-thing is indeed a hard (and interesting) problem > to solve (but would be easy to detect). > > --felix > > Am Donnerstag 13 September 2012 00:02:45 schrieb Thomas Reinke: > > We're running into a hiccup with openvassd (rls 5) that I wouldn't > > mind getting some feedback on. > > > > After upgrading both scanner and scripts, and removing > > find_service.nes from the plugins directory so that there was no > > possibility of confusion with find_service.nasl and the built in > > find_service plugin, a look at the openvassd.messages log is showing > > that find_service.nasl is being launched BEFORE nmap.nasl. > > > > My understanding is that nmap.nasl, with a category of ACT_SCANNER, > > should ALWAYS execute before something like find_service.nasl, with > > a category of ACT_GATHER_INFO. > > > > Is there something I'm missing? Shouldn't all ACT_SCANNER class > > scripts be COMPLETELY finished, regardless of user config, before > > other categories start firing up? This is preventing > > find_service.nasl from working correctly. > > > > Thomas -- Michael Wiegand | Greenbone Networks GmbH | http://www.greenbone.net/ Neuer Graben 17, 49074 Osnabrück, Germany | AG Osnabrück, HR B 202460 Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-devel ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2221 / Virus Database: 2437/5274 - Release Date: 09/17/12 _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-devel
