On Dec 18, 2007, at 10:04 AM, Sam Stern wrote:
>
>>> I would log this as a bug against the gpl version
>>
>> I'd consider this as a bug in the distro.
>> Shipping a broken or incompatible bison with the same command name is
>> not a great idea.
>
> I posted only because this problem has been reported to this list
> before and no solution ever offered. So I posted my solution knowing
> it's a problem that his hit a small number of others over the years
> that Nessus has been around and there is no evidence the problem
> ever got solved. Thus I posted just to provide a direction for
> anyone else who ever ran into the problem. Everyone else is invited
> to simply ignore the posting as not relevant to the majority of
> users :>
Thank you Sam. For reference, another cause for the error "cannot
parse plug-in" is that an empty plugin can cause this same message.
This may occur after doing a plugin update on a full disk or when
interrupting the installation process.
-- Renaud
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
