Am Dienstag, 9. Oktober 2012, 16:39:34 schrieb Matthew Toseland:
> On Tuesday 09 Oct 2012 13:10:43 guido wrote:
> > Am Dienstag, 9. Oktober 2012, 10:33:35 schrieb Matthew Toseland:
> Well each one lasts less than a seconf and they are happening much less than
> once per second. So no, that's not a
I can confirm the described behaviour.
My system:
Linux on x86_64, Java 1.6.0_07-b06.
The downloads were started with frost, but they have not been inserted by
Frost.
Guido
Am Freitag, 14. November 2008 23:01:27 schrieb Victor Denisov:
> Several downloads from my download queue failed t
I can confirm the described behaviour.
My system:
Linux on x86_64, Java 1.6.0_07-b06.
The downloads were started with frost, but they have not been inserted by
Frost.
Guido
Am Freitag, 14. November 2008 23:01:27 schrieb Victor Denisov:
> Several downloads from my download queue failed t
Hi,
After moving my node to a different computer, I cannot start it using the
wrapper anymore. After running ./run.sh start, the node won't come up and
after some waiting time, all the processes associated with freenet (i.e. all
the java processes on this system) will disappear.
I can start it
Hi,
After moving my node to a different computer, I cannot start it using the
wrapper anymore. After running ./run.sh start, the node won't come up and
after some waiting time, all the processes associated with freenet (i.e. all
the java processes on this system) will disappear.
I can start it
I have now "solved" the problem by removing the datastore. I can now run the
node again, but I'm afraid whatever bug caused this in the first place is
most likely still there and I might well run into the same or similar
problems in the future when the store/cache grows again.
For the time bein
I have now "solved" the problem by removing the datastore. I can now run the
node again, but I'm afraid whatever bug caused this in the first place is
most likely still there and I might well run into the same or similar
problems in the future when the store/cache grows again.
For the time bein
lso prevent the store+cache temporarily using more than the
> specified limit.
>
> On Wed, Nov 01, 2006 at 05:07:35PM +0100, Guido Winkelmann wrote:
> > Am Samstag, 28. Oktober 2006 17:43 schrieb Guido Winkelmann:
> > > Hi,
> > >
> > > Am Donnerstag, 26
lso prevent the store+cache temporarily using more than the
> specified limit.
>
> On Wed, Nov 01, 2006 at 05:07:35PM +0100, Guido Winkelmann wrote:
> > Am Samstag, 28. Oktober 2006 17:43 schrieb Guido Winkelmann:
> > > Hi,
> > >
> > > Am Donnerstag, 26
Am Samstag, 28. Oktober 2006 17:43 schrieb Guido Winkelmann:
> Hi,
>
> Am Donnerstag, 26. Oktober 2006 22:53 schrieben Sie:
> [...]
>
> > Bizarre.
> >
> > The first time, it takes from 00:13:10 to 01:14:15 *the next day* (so
> > around 25 hours) to read half
Am Samstag, 28. Oktober 2006 17:43 schrieb Guido Winkelmann:
> Hi,
>
> Am Donnerstag, 26. Oktober 2006 22:53 schrieben Sie:
> [...]
>
> > Bizarre.
> >
> > The first time, it takes from 00:13:10 to 01:14:15 *the next day* (so
> > around 25 hours) to read half
Hi,
Am Donnerstag, 26. Oktober 2006 22:53 schrieben Sie:
[...]
> Bizarre.
>
> The first time, it takes from 00:13:10 to 01:14:15 *the next day* (so
> around 25 hours) to read half of the store. The second time it takes from
> 01:18:04 to 03:11:33 (2 hours) to read the entire store. There's
> somet
Hi,
Am Donnerstag, 26. Oktober 2006 22:53 schrieben Sie:
[...]
> Bizarre.
>
> The first time, it takes from 00:13:10 to 01:14:15 *the next day* (so
> around 25 hours) to read half of the store. The second time it takes from
> 01:18:04 to 03:11:33 (2 hours) to read the entire store. There's
> somet
Hi,
Last week, I had to stop my node for a short time and then I restarted it
again. To my surprise, I had to wait more than 24 hours (!!) before I could
use the node again.
Here is a part of wrapper.log:
http://freenet.thisisatest.de/part%20of%20wrapper.log
Note the timestamps.
The same thi
Hi,
Last week, I had to stop my node for a short time and then I restarted it
again. To my surprise, I had to wait more than 24 hours (!!) before I could
use the node again.
Here is a part of wrapper.log:
http://freenet.thisisatest.de/part%20of%20wrapper.log
Note the timestamps.
The same thi
Am Donnerstag, 27. Juli 2006 09:45 schrieb Ortwin Regel:
> You could always change your nodename to "I'll be back" or something before
> you leave, then people connected at that time can see that you are just
> away temporarily. That's what I was planning to do.
Or send them a short node2node mess
Am Donnerstag, 27. Juli 2006 09:45 schrieb Ortwin Regel:
> You could always change your nodename to "I'll be back" or something before
> you leave, then people connected at that time can see that you are just
> away temporarily. That's what I was planning to do.
Or send them a short node2node mess
up when the db gets backed up. If it's flat-file based, you have
to copy over the flat files...
> On Wed, Nov 23, 2005 at 10:02:18PM +0100, Guido Winkelmann wrote:
[Announcement of new wiki]
Guido
--
Mailing list archives are not a proper form of documentation.
up when the db gets backed up. If it's flat-file based, you have
to copy over the flat files...
> On Wed, Nov 23, 2005 at 10:02:18PM +0100, Guido Winkelmann wrote:
[Announcement of new wiki]
Guido
--
Mailing list archives are not a proper fo
Hi,
As many of you might have noticed, the Freenet wiki had been offline for
several weeks now. I turns out that the reason behind this was a site-wide
database upgrade from mysql 3 to mysql 4 at Sourceforge, which broke many
things.
The bad news is that, apparently, there is no way to get at
Hi,
As many of you might have noticed, the Freenet wiki had been offline for
several weeks now. I turns out that the reason behind this was a site-wide
database upgrade from mysql 3 to mysql 4 at Sourceforge, which broke many
things.
The bad news is that, apparently, there is no way to get at
21 matches
Mail list logo
