Well, in this case, this is only for Links 2.0.
In this version, for example for the quick link check, nph-verify.cgi uses UserAgent.pm at LWP\Parallel to verify links. If nph-verify.cgi does not find LWP, then it uses an alternative but slow method after the following error message:
"Unable to load Parallel User Checker. System Error:
Can't locate LWP/Parallel/UserAgent.pm in @INC (...) [snip]
Using IO::Socket method instead."
Renaming Lwp to LWP works well instead. (This has happened with my website today, on a Unix server).
In this version, for example for the quick link check, nph-verify.cgi uses UserAgent.pm at LWP\Parallel to verify links. If nph-verify.cgi does not find LWP, then it uses an alternative but slow method after the following error message:
"Unable to load Parallel User Checker. System Error:
Can't locate LWP/Parallel/UserAgent.pm in @INC (...) [snip]
Using IO::Socket method instead."
Renaming Lwp to LWP works well instead. (This has happened with my website today, on a Unix server).
