On 20 Sep 2002 at 10:52, Kundu, Partha wrote: > Hi Robert, > > Could it be (parsing stop in default spider progress window) because the > buffer is too small? I've noticed that is happens if the 'limit' is > increased. > > Enclosed is the log file. Pls let me know if you have any questions. > > -Partha
Hi Partha, Thanks for the help. It does seem something along those lines. It seems to be the output from Bmp2TBmp that is causing the stop. The stderr from TBmp2Bmp doesn't get put onto the progress dialog, but you can see it in the DOS console. The reason for that is that we are only catching the output from the python parser, not Bmp2TBmp. What is the effect when you turn the spidering verbosity down to 0 and 1 (Minimum and Medium) instead of 2 (Maximum) and parse that same CNN site? On Wired, it solved the problem. Also, what is the effect if you parse your CNN site with images turned off on the different verbosities? (Further evidence that the output from Bmp2TBmp is the cause). If it is the cause, then work can be done to address this. Best wishes, Robert _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
