On Tue, Feb 03, 2004 at 04:32:24PM +0100, Hugo van der Kooij wrote: > > I just noticed a scan was incomplete due to a large number of SIGSEGV errors > > in the nessus messages log. The software was installed recently from the RPM > > files of atrpms: > > > > Packages: > > libnessus-2.0.10a-11.rhfc1.at > > nessus-2.0.10a-14.rhfc1.at > > nessus-server-2.0.10a-14.rhfc1.at > > libnasl-2.0.10a-15.rhfc1.at > > nasl-2.0.10a-15.rhfc1.at > > > > Is this a known limitation?
> I hope not. Could you rpm -V the packages? Perhaps the notorious > prelinking rpm corruption? The machine is a standard up2date FC1 machine. (No testing packages.) The command did not show anything odd. Just a load of updated NASL scripts. But that brings me to the issue I had with the nessus-plugins-update script. It failed to update because wget inside the script added an .1 to the filename which did not occur when I did the exact same wget command from the commandline. I added a mv command to get rid of the .1 added to the file it downloaded. I noticed some of the nasl scripts are in unix format and some in dos format. Might this have any impact? Hugo. -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
