Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/20/d268022878/htdocs/forum/viewtopic.php on line 988

Strict Standards: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/20/d268022878/htdocs/forum/viewtopic.php on line 988
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4284: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4286: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4287: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4288: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
FAROO Forum • View topic - Crawler queue updates
Page 1 of 1

Crawler queue updates

PostPosted: Wed Oct 02, 2013 7:08 pm
by TomHH
We are all aware of the problem with deadlocks of the Faroo p2p client. This is mentioned in many (open :shock: ) posts in this forum.
I observed that in many cases (if not all?) the crawler queue at restart of the client is the same as at the last start. In other words: the queue is not updated during working time of the client. It seems to be updated only at shutdown time. Restarting a previously crashed client results in repeating previously crawled, indexed and distributed web page content. In my opinion, this is a waste of time and ressources. The only benefit of this behaviour is that indexed words are distributed to other peers than at the first time broadening the overall database.
However, I would like to see interim updates of the crawler queue so that a restart after a crash does not imply a repetition of all pages.

Re: Crawler queue updates

PostPosted: Fri Nov 01, 2013 7:09 pm
by TomHH
Four weeks after my post still no reaction from the Faroo team. :shock: