In Reply To:
You might also look at the setting you can adjust in nph-verify.cgi and see if you can overcome this problem.
Can you please elaborate on this?
I was very excited to see the new nph-verify.cgi, but unfortunately it still will not run for me. My DB is ~400kb with 1300 links. Verify now seems to stop on #120 via the browser and #12 via telnet...
When run via the browser, #120 reads
Checked <a href="http:/
and that is where it is cut off.
My problem with the old nph-verify.cgi was that:
In Reply To:
I strace() the program and found it hanging on the following IP:
216.3.41.56
It should timeout and resume operation, but for some unknown reason, the Links include perl modules/libraries are in fact not timing out...
For some reason, the alarm() is set, but somewhere in your program that signal $SIG{'ALRM'} is being masked...
You may want to use our FQuest core modules instead as LWP is fully installed, as well as many many others...
That specific IP's record was removed from the links.db, but my guess is that the new nph-verify is also having a similar problem.
Does anyone know more about $SIG{'ALRM'}?
Or, how would I go about using my host's core modules or is this even as relevant to the new nph-verify.cgi?
Thanks for any ideas.