Can someone point me in the correct direction for correcting a time out problem when verify links is done.

I have a little over 2100 links and it times out at about #200

Thanks!

Install Bobsie's deadlink report mod and run nph-verify.cgi from telnet. If you don't have telnet, you could install perl and a server on your pc.

--Drew

Does Bobsie's deadlink report mod actually affect to functionality of nph-verify.cgi? Or are you suggesting the two stages as two seperate remedies (1) Mod (2) run from telnet.

Adam

Bobsie's code modifies the script, and telnet is a different form of access to the scripts on your server. Telnet won't time out like your browser.

HTH

DT

Yes, I know about telnet. Even that was giving me problems with my host because evidently there is still a timeout period. So I added a linux server on another hard drive to run verify that way.

That's why I was wondering if Bobsie's mod enhances the ability of the verify script when run through telnet.

Adam

No...it does not.

Regards,

Eliot Lee

It simply saves the output to a file since you can't do anything with it from telnet.

--Drew

I am trying to solve a timeout issue on links2.0 (I currently have about 2000 links loaded). Can someone tell me what this Bobsie's deadlink report mod is and how can I get it. Specifically -does it replace nph-verify.cgi and will it save out to an html file so I can manage the dead links? Is this a real popular customization? Has anyone solved the timeout issue with anything else? Would the situation improve if I went to LinksSQL?

Thanks.