That's certainly fair. I'll try to get that for you, but I'll need some instruction or time to research how to do this.
Alternatively, I can make available my vmware appliance with that base installation set running. I did stumble upon some news that might help things. I was frustrated and I wiped out my entire /usr/lib/openvas/plugins directory and ran openvas-nvt-sync to make sure only the exact feed contents were being run, and the tests ran through without the error. Also, I received much less trouble from starting openvasd because dependencies were all met. Perhaps there are outdated or incomplete plugins in the plugins rpm? On the downside, I'm missing port scanners and a huge number of checks, which makes sense because the feed seems to contain the Debian local security checks only (according to http://www.openvas.org/openvas-nvt-feed.html). Sorry if I sound needy - I really want to understand the project and its inner workings, and I'd really like to help it grow in any way I can. On Fri, Aug 15, 2008 at 12:07 PM, Tim Brown <[EMAIL PROTECTED]>wrote: > On Friday 15 August 2008 16:50:41 Patrick Hornung wrote: > > I can't imagine everyone is having the SIGSEGV error, right? Are there > > tests I should be avoiding? > > > > I've rebuilt my entire test system again using Fedora 9 and the > unofficial > > repository listed in the instructions. I can't seem to run a single test > > on a single host without a SIGSEGV appearing at the end of the openvas > log. > > If it matters, running a test with no port scanner and no plugins > > completes without the error (although it's a rather useless test). > > Noone has yet sent me the debug out I was after. Without that it's not > trivial to identify the route cause. > > Cheers, > Tim > -- > Tim Brown > <mailto:[EMAIL PROTECTED]> > <http://www.nth-dimension.org.uk/> >
_______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
