Re: Re[2]: [freenet-support] unable to start after disk filled

2003-11-25 Thread Brian T. Schellenberger
I'd tried doing an update, and that didn't fix it, so I just wipeed EVERYTHING and started over. Probably over-drastic, but it worked. On Monday 24 November 2003 10:34 am, Aureliano Rama wrote: | I think as well that he should get a new copy of freenet.jar, that | surely doesn't hurt nor

Re: [freenet-support] Question on IPNetRouter for Macintosh

2003-11-25 Thread Jan
Toad wrote: On Tue, Nov 18, 2003 at 02:45:27PM +0100, Jan wrote: [...] Guess I need to leave Freenet running in hope of better times. When there will be a Mac OS9 version, perhaps. Technically you can run it on OS/9... you need a 1.4 JDK, and a command line, though. I don't have a mac

[freenet-support] Unable to start after an insert

2003-11-25 Thread Thad Eckard
I just realized that I think I'm having a problem. I made an insert over the night, woke up and stopped Freenet for about two minutes, then tried to re-start it. Now, Freenet keeps trying to start with no success. The blue arrowhead objects behind the rabbit just keep running up. I'm using

Re: [freenetproject@gl00on.net: [freenet-support] Unable to establish loopback connection]

2003-11-25 Thread Toad
On Tue, Nov 25, 2003 at 10:18:31PM +0100, [EMAIL PROTECTED] wrote: Hi everyone, the following problem (which I reported earlier) continues to persist in the latest stable build. Any ideas on what might go wrong here and how to fix it would be appreciated. Attempting to start up freenet

RE: [freenet-support] Freenet Stable Build 5030

2003-11-25 Thread Kevin Bennett
Gah, replied to the wrong damn thread. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kevin Bennett Sent: 25 November 2003 22:29 To: [EMAIL PROTECTED] Subject: RE: [freenet-support] Freenet Stable Build 5030 FYI: After running this version for 50 mins,

RE: [freenet-support] Freenet stable build 5041

2003-11-25 Thread Kevin Bennett
FYI: After running this version for 50 mins, all activity abruptly stopped. Input and output went from 56k/20k to 5k/0k over a period of 2 minutes. No response from localhost: either yet the node was apparently still running as there were dozens of these log entries: