OK, good tip! Your idea brought me indirectly to dumping the openvasd cofnig. I did;
./openvasd -d which showed me the new version of the OpenVAS daemon was using libraries from an older version of OpenVAS (2.0.1). That in turn got me looking at my ld.so.conf file, in which I had a path to the older version of OpenVAS. Once I removed the older references it now works like a charm. Thanks to all who responded. Cheers, Mark --- On Fri, 9/18/09, Jan-Oliver Wagner <[email protected]> wrote: From: Jan-Oliver Wagner <[email protected]> Subject: Re: [Openvas-discuss] Problem with OpenVAS 2.0.3 To: [email protected] Received: Friday, September 18, 2009, 1:57 PM On Friday 18 September 2009 14:47:39 Isabella Disley wrote: > I am using 2.0.4. > These are the packages I installed; you can use ldd to check which libs are linked. $ ldd openvasd If you don't rember where it is instsalled, this might work on your system: $ ldd `which openvasd` Best Jan -- 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] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
_______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
