"Harik A'ttar" writes:
> very quickly (and start timing out, thread loss, etc). A number of
> people are hoping it's blocking IO vs Non-Blocking, since that's
> fixable.
Sorry to reply to my own message, but I've been thinking about it
and the more I think about it, the more sense it makes.
> What he's saying is "For some reason, it's taking 50-60 generally high
> end machines on dedicated connections to do the work of one 386-33 on a
> 9600 baud modem." Something is very broken, causing nodes to overload
> very quickly (and start timing out, thread loss, etc). A number of
> peo
Anyone have a lock of sorts under Contrib/fcptools ?
--
Jay Oliveri "In the land of the blind,
Systems Architect the one-eyed man is king."
GnuPG ID: 0x5AA5DD54
(remove v+p for real email)
On Fri, 14 Jun 2002, u Uler wrote:
> When you say, "it should not be possible to stop Freenet by overloading," do
> you mean that even if there are too few permanent nodes, the Freenet
> protocol should be designed so that the network isn't stopped? Or do you
> mean that we need more permanent no
On Thu, 13 Jun 2002, Dave Hooper wrote:
> I've never had a problem before, (in fact I don't see any problem at my
> end).
> What *might* be happening is that my cvs client, by default, is using
> unix-style line endings for text files (files without the -kb flag), which
> is absolutely fine for V
Because of the recent changes in watchme code (the addition of the HTL
field in logs and fixes to the date format), I'm forcing watchme node
owners to update. The new snapshot is being generated now and the
server will be changed tonight to require a new watchme version.
Everyone should update A
