On Montag, 30. März 2015, Russell Jones wrote: > Just wanted to bump this back up to the top in hopes of a response. Is > this a bug in the logic that the openvas-manager is not rebuilt after > updating the feed?
At least it looks a bit strange. Not sure what the authors intention is. However, there exists another way to let OpenVAS Manager do a rebuild: Sending a HUP singal to the main openvasmd process. The feed update scripts do so for example. > On 3/23/2015 3:21 PM, Russell Jones wrote: > > Thanks, this seems to have resolved it! > > > > I noticed in the cron job for updating the plugins exists the > > following logic: > > > > if [ "$notify_openvas_scanner" == "yes" ]; then > > /etc/init.d/openvas-scanner restart > /dev/null 2>&1 > > if [ ! -f /var/lib/openvas/mgr/tasks.db ]; then > > /usr/sbin/openvasmd --rebuild > /dev/null 2>&1 > > else > > /etc/init.d/openvas-manager restart > /dev/null 2>&1 > > fi > > > > > > I do have a tasks.db file, so it looks like the rebuild command is not > > being sent. Any ideas why the logic is like this if openvas-manager > > needs to be rebuilt after updating the plugins? -- Dr. Jan-Oliver Wagner | +49-541-335084-0 | http://www.greenbone.net/ Greenbone Networks GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 202460 Geschäftsführer: Lukas Grunwald, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
