Several reports are only created at end of crawl (very
end when all threads have terminated). Sometimes a
crawl will encounter an error that makes it impossible
to achive this state (threads hung or otherwise unable
to be reported as terminated). In those instances it
would be very usefull to have an option to force the
writing of those reports. The same code could probably
also be used to automatically write those reports when
error conditions known to halt crawling occurs (such as
out of memory).
Michael Stack
None
None
Public
|
Date: 2007-03-14 01:31
|
|
Date: 2004-10-25 16:34 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2004-10-25 16:34 | stack-sf |
| close_date | - | 2004-10-25 16:34 | stack-sf |
| assigned_to | nobody | 2004-10-21 19:47 | gojomo |
| priority | 6 | 2004-10-21 19:45 | gojomo |
| priority | 5 | 2004-09-01 21:55 | gojomo |
| priority | 6 | 2004-07-07 21:54 | gojomo |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use