This has always been slow (our server won't do parallel checks), but since our ISP moved over to Apache (which may be coincedental) the link checks crash after 100 to 427 (our best!) checked links. (We have c.600 links.)
The nph page just stops writing mid line.
Is there (i) a 'cure' or (ii) an easy way of doing a staggered check?

Yea...Run the nph-verify.cgi via telnet.

It will not time-out as much as executing the file via your web browser.

Regards,

------------------
Eliot Lee
Anthro TECH,L.L.C
www.anthrotech.com
----------------------

Thanks.
However I only have HTTP and FTP access to our server.
I could (i.e. think I 'can') modify the nph-verify script to stagger it, but did not want to "re-invent the wheel" (nor solve what was only an imagined problem).
(The server copes with seemingly longer NPH/CGI scripts -e.g. bulk e-mailings(?).)
Michael Chapman.

Oooops, this path has been trod before.
Haven't studied it, but <http://goodstuff.orphanage.com/BadLinksRpt.html> looks promising.

yeah... of course. Aside from not being able to run the scripts at all (both Links' and Bobsie's link checker), I don't think they could handle the 7500 links I need verified. Also, found another link checker (the one I mentioned before sucks):
http://www.biggbyte.com/infolink/

I have the same problem...in fact I just finished downloading some Windows software from Tucows.com for link checking. It's called "CyberSpyder" and I think there were two or three other programs available.

The nice thing about verifying from within Links is that it is then very easy to edit the faulty/broken links within the same database. (It is more often a slightly changed address within a site rather than a deadlink.)
The 'verifier' in Links provided a nice summary at the end. Staggering would lose that (without some neat code work, to store and then later build the summary). (We often have multiple links to (different pages) within a site, so a global summary is useful for spotting what is going wrong.)

? Scope for an official patch ?