On 15-07-2015 11:21, Reindl Harald wrote:
However, the main question is: why the hell did the openvas installation
get bricked just because one of the processes was killed, and how can I
recover from this without reinstalling the whole guest OS? Isn't it the
job of openvas-check-setup to find this kind of problems?
no it's not the job of "openvas-check-setup" to fix bricked
installations with a completly unknown state after random processes
got killed by the kernel in the middle of operations - no software can
fix that
My understanding is that this "completely unknown state" is stored in de
filesystem in the form of files, so it isn't "completely random" after
all. If openvas stops working and even after a reboot the problem
persists then this must mean that some kind of corruption happened to
openvas-related files as a result of the crash... And isn't it the job
of openvas-check-setup to check openvas-related files, after all?
I understand that a simple script can't check and fix everything (some
details must be hidden deep inside thousands of binary files), but in
that case don't tell me that the purpose of openvas-check-setup if not
to find this kind of problems.
Normally software can tollerate crashes and don't need a reformat to fix
problems. That's the general rule.
João Jerónimo
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
