James A. Treacy wrote: > On Sun, May 13, 2001 at 03:21:28PM +0200, Martin Schulze wrote: > > Something strange I noticed while reading urlcheck's output: > > > > | Looking into http://www.debian.org/events/2001/0504-linuxtag-braunschweig > > | http://braunschweiger.linuxtage.de/ : IOError: gave up on site (15 > > second limit) > > | http://braunschweiger.linuxtage.de/ : IOError: gave up on site (15 > > second limit) > > | http://braunschweiger.linuxtage.de/ : IOError: gave up on site (15 > > second limit) > > > > What's that? Some connection limit? If so could urlcheck be advised > > to check such an address later? Additionally, could urlcheck cache > > pages? > > > The default timeout is quite long (2min?) and causes the script to take an > incredibly
Doh! > long time to run so I used a signal to shorten it. The message shows the time > before > timing out, so if the site actually works you can ignore the message. Yes, it works. There are just a lot of such reports produced by urlcheck and it takes quite a while checking all of them. > > > | Looking into http://www.debian.org/events/2001/0704-debcon > > | http://www.debian.org/events/2001/0704-debcon.fr.html : Error = (404) > > Not Found > > > > That's quite strange, some apache problem? > > > > | Looking into http://www.debian.org/events/2001/ > > | http://www.debian.org/events/2001/index.fr.html : Error = (404) Not > > Found > > > > Problem on www.debian.org. > > > I suspect both of these will not show up on the next run. When will that be? > Soon, I hope (have to make a few changes before the next run). Regards, Joey -- Life is too short to run proprietary software. -- Bdale Garbee
