On Monday 07 Nov 2011 22:13:30 Dave Riley wrote:
I use an Intel iMac running 10.6.8. I used freenet.jnlp, then
new_installer_offline_1404.jar to Install the Freenet directory onto a 3GB
TrueCrypt volume, and the tray into /Applications -- this configuration
worked fine in an iMac PPC
Sorry folks, don't use 1231 (fortunately the upload to the auto-update didn't
complete), it had a severe bug preventing startup. 1232 fixes this and also has
some minor work on plugins.
signature.asc
Description: This is a digitally signed message part.
Please upgrade to 1231. Changelogs:
1229:
- XML vulnerability warnings fixes.
- Fix an NPE in plugins.
- Minor internal stuff.
1230:
- Detect the XML vulnerability on OS/X. Try to detect it on OpenJDK, maybe not
very well.
- Clarify an english string (Completed downloads to temporary space not
Freenet 0.7 build 1228 is now available. Apologies for not posting a changelog
for 1227, I will now. Please upgrade ASAP as 1228 is mandatory on Friday and
warns the user about a critical security problem in Sun JVMs.
1228:
- Warn user about, and refuse to load plugins handling XML, a severe
Freenet 0.7 build 1225 is now available (1224 originally, 1225 and 1226 fix
regressions, sorry). Many changes, the most important ones being:
- Finally fix the attack identified by The Register *four years* ago, by not
caching data requested either locally or nearby. This is also necessary in
Freenet 0.7 build 1217 is now available, please upgrade. This build will
probably be 0.7.5-beta1. Changes are minimal:
- Translation updates to German and Italian, change Chat and Chat Forums to
Discussion and Forums.
- Work around overflowing progress bars.
- Link to the FAFS pages on Frost and
Freenet 0.7 build 1218: last minute fixes:
- Don't use javascript on the progress page on Chrome and Safari, as it doesn't
work (the progress page stalls).
- Bookmark edition updates.
- Fix the confirmation page for setting high friends security level, was
showing the wrong string.
- Spell
On Monday 01 June 2009 22:33:29 SmallSister development wrote:
Another issue: I have several downloads that report being at 100%,
but they'll never report completed; even over freenet restarts.
This could be caused by a freenet crash while in the process of
writing out the files. (using
On Wednesday 27 May 2009 15:41:47 SmallSister development wrote:
Matthew Toseland wrote:
Freenet 0.7 build 1212 is now available. Please upgrade.
[...]
1212: - Recently we have had several reports of bogus claims by peers
that the auto-update key has been blown. The nodes would not
Freenet 0.7 build 1210 is out. Sorry for the delay in announcing it. It will
be mandatory at midnight. There was also a minor git mess relating to
tagging - it was released from a local branch because I forgot to push before
tagging, although it has been merged back into master now. If you are
On Fri, 1 May 2009 11:23:39 -0400, Dennis Nezic wrote:
> On Thu, 30 Apr 2009 19:08:30 +0100, Matthew Toseland wrote:
> > In other news, Freenet has moved from using Subversion to keep its
> > source code to Git.
>
> What's the link to the git repository? (Maybe the website should be
> updated to
On Thu, 30 Apr 2009 19:08:30 +0100, Matthew Toseland wrote:
In other news, Freenet has moved from using Subversion to keep its
source code to Git.
What's the link to the git repository? (Maybe the website should be
updated to include it?)
___
Support
On Fri, 1 May 2009 11:23:39 -0400, Dennis Nezic wrote:
On Thu, 30 Apr 2009 19:08:30 +0100, Matthew Toseland wrote:
In other news, Freenet has moved from using Subversion to keep its
source code to Git.
What's the link to the git repository? (Maybe the website should be
updated to include
Freenet 0.7 build 1209 is out (sorry it took so long, I understand there were
some fairly bad bugs in 1208). Please upgrade. Lots of changes, including:
- Lots of bugfixes related to the db4o merge.
- A progress page shown when a page or file fetched through fproxy will take
more than 5 seconds
Freenet 0.7 build 1209 is out (sorry it took so long, I understand there were
some fairly bad bugs in 1208). Please upgrade. Lots of changes, including:
- Lots of bugfixes related to the db4o merge.
- A progress page shown when a page or file fetched through fproxy will take
more than 5 seconds
I released 1207 yesterday, but didn't insert it to the auto-updater. At the
time new nodes were failing to load any of the default plugins. I discovered
that there was a bug breaking FCP inserts in 1207, so fixed it and released
1208, and have now started both inserting to the auto-updater.
I released 1207 yesterday, but didn't insert it to the auto-updater. At the
time new nodes were failing to load any of the default plugins. I discovered
that there was a bug breaking FCP inserts in 1207, so fixed it and released
1208, and have now started both inserting to the auto-updater.
Freenet 0.7 build 1205 is now available. Please upgrade. Mostly this is
optimisations and minor bugfixes. There are also some changes related to
inserting big freesites (or librarian indexes), backported from the db4o
branch, and some minor changes.
If you find a bug, please let us know!
Freenet 0.7 build 1205 is now available. Please upgrade. Mostly this is
optimisations and minor bugfixes. There are also some changes related to
inserting big freesites (or librarian indexes), backported from the db4o
branch, and some minor changes.
If you find a bug, please let us know!
On Saturday 24 January 2009 18:18, Dennis Nezic wrote:
> On Sat, 24 Jan 2009 18:07:24 +, Matthew Toseland wrote:
> > fproxy can still be probed for, just not individual sites... We
> > should also warn about it in the README...
>
> You mean the executable/jar can still be probed for on the
On Saturday 24 January 2009 17:41, Dennis Nezic wrote:
> On Sat, 24 Jan 2009 13:05:41 +, Matthew Toseland wrote:
> > There have been some question marks over whether it is possible to
> > load an image from an external domain and get a callback when it is
> > loaded - if so, it may be possible
On Sat, 24 Jan 2009 18:07:24 +, Matthew Toseland wrote:
> fproxy can still be probed for, just not individual sites... We
> should also warn about it in the README...
You mean the executable/jar can still be probed for on the filesystem?
Maybe. But it can't be done via the network interface,
On Friday 23 January 2009 01:53, [Anon] Anon User > wrote:
> -BEGIN TYPE III ANONYMOUS MESSAGE-
> Message-type: plaintext
>
> In Matthew Toseland wrote:
>
> >>> > > The real solution to browser history stealing is simply to use a
separate
> >>> > > browser for Freenet than the one you
On Sat, 24 Jan 2009 13:05:41 +, Matthew Toseland wrote:
> Meaning running a web browser on a system with access to fproxy is
> dangerous. I haven't tested this, maybe you'd like to?
I would imagine that the same problem exists on a system with access to
fcp? or telnet if it's enabled? Ie.
On Sat, 24 Jan 2009 13:05:41 +, Matthew Toseland wrote:
> There have been some question marks over whether it is possible to
> load an image from an external domain and get a callback when it is
> loaded - if so, it may be possible to time fetches of specific sites
> from javascript on an
-BEGIN TYPE III ANONYMOUS MESSAGE-
Message-type: plaintext
In Matthew Toseland t...@amphibian.dyndns.org wrote:
The real solution to browser history stealing is simply to use a
separate
browser for Freenet than the one you use for the wider web. We now warn
users
about
On Friday 23 January 2009 01:53, [Anon] Anon User wrote:
-BEGIN TYPE III ANONYMOUS MESSAGE-
Message-type: plaintext
In Matthew Toseland t...@amphibian.dyndns.org wrote:
The real solution to browser history stealing is simply to use a
separate
browser for Freenet than the
On Sat, 24 Jan 2009 13:05:41 +, Matthew Toseland wrote:
There have been some question marks over whether it is possible to
load an image from an external domain and get a callback when it is
loaded - if so, it may be possible to time fetches of specific sites
from javascript on an
On Sat, 24 Jan 2009 13:05:41 +, Matthew Toseland wrote:
Meaning running a web browser on a system with access to fproxy is
dangerous. I haven't tested this, maybe you'd like to?
I would imagine that the same problem exists on a system with access to
fcp? or telnet if it's enabled? Ie.
On Saturday 24 January 2009 17:41, Dennis Nezic wrote:
On Sat, 24 Jan 2009 13:05:41 +, Matthew Toseland wrote:
There have been some question marks over whether it is possible to
load an image from an external domain and get a callback when it is
loaded - if so, it may be possible to
On Sat, 24 Jan 2009 18:07:24 +, Matthew Toseland wrote:
fproxy can still be probed for, just not individual sites... We
should also warn about it in the README...
You mean the executable/jar can still be probed for on the filesystem?
Maybe. But it can't be done via the network interface, if
On Saturday 24 January 2009 18:18, Dennis Nezic wrote:
On Sat, 24 Jan 2009 18:07:24 +, Matthew Toseland wrote:
fproxy can still be probed for, just not individual sites... We
should also warn about it in the README...
You mean the executable/jar can still be probed for on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland wrote:
> On Thursday 22 January 2009 22:30, Ancoron Luciferis wrote:
>> Matthew Toseland wrote:
>>> Freenet 0.7 build 1203 is now available. Please upgrade.
>>>
>>> The main change in 1203 is that history cloaking is removed. It is
-BEGIN TYPE III ANONYMOUS MESSAGE-
Message-type: plaintext
In Matthew Toseland wrote:
>>> > > The real solution to browser history stealing is simply to use a
>>> > > separate
>>> > > browser for Freenet than the one you use for the wider web. We now warn
> users
>>> > > about this
On Thursday 22 January 2009 22:30, Ancoron Luciferis wrote:
> Matthew Toseland wrote:
> > Freenet 0.7 build 1203 is now available. Please upgrade.
> >
> > The main change in 1203 is that history cloaking is removed. It is very
messy
> > code-wise and does not really solve the problem - for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland wrote:
On Thursday 22 January 2009 22:30, Ancoron Luciferis wrote:
Matthew Toseland wrote:
Freenet 0.7 build 1203 is now available. Please upgrade.
The main change in 1203 is that history cloaking is removed. It is very
messy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland wrote:
> Freenet 0.7 build 1203 is now available. Please upgrade.
>
> The main change in 1203 is that history cloaking is removed. It is very messy
> code-wise and does not really solve the problem - for example, if a user
> posted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Toseland wrote:
Freenet 0.7 build 1203 is now available. Please upgrade.
The main change in 1203 is that history cloaking is removed. It is very messy
code-wise and does not really solve the problem - for example, if a user
posted the
On Thursday 22 January 2009 22:30, Ancoron Luciferis wrote:
Matthew Toseland wrote:
Freenet 0.7 build 1203 is now available. Please upgrade.
The main change in 1203 is that history cloaking is removed. It is very
messy
code-wise and does not really solve the problem - for example, if a
Freenet 0.7 build 1203 is now available. Please upgrade.
The main change in 1203 is that history cloaking is removed. It is very messy
code-wise and does not really solve the problem - for example, if a user
posted the key for something they had inserted, and forgot to remove
the ?secureid=
Freenet 0.7 build 1203 is now available. Please upgrade.
The main change in 1203 is that history cloaking is removed. It is very messy
code-wise and does not really solve the problem - for example, if a user
posted the key for something they had inserted, and forgot to remove
the ?secureid=
Freenet 0.7 build 1199, 1200 and 1201 are now available (sorry, I needed some
changes to Freenet for the new installer...). Please upgrade to 1201. Also,
there have been some important changes to the installer.
1199:
- Minor changes to turtling: Backoff from nodes which send a turtle transfer
Freenet 0.7 build 1198 is now available, and will be mandatory at midnight
GMT.
The main change is request turtling. This is an attempt to reduce the average
request latency by cutting off request transfers at 60 seconds - we cancel
the downstream transfers, and backoff the node, but let it
Freenet 0.7 build 1197 is now available, and is mandatory at midnight. Please
upgrade. Nodes with auto-deploy-update disabled may have problems, since in
1195 a bug was introduced which broke the Update Now button, which is fixed
in 1197. If you are in this situation please either update
Freenet 0.7 build 1196 is now available, and is mandatory. It should be
downloaded by your node automatically. Please upgrade.
We are still working on the request latency optimisations that we started on
Saturday. We have discovered that the median time taken by a typical CHK
request is vastly
Freenet 0.7 build 1197 is now available, and is mandatory at midnight. Please
upgrade. Nodes with auto-deploy-update disabled may have problems, since in
1195 a bug was introduced which broke the Update Now button, which is fixed
in 1197. If you are in this situation please either update
Freenet 0.7 build 1196 is now available, and is mandatory. It should be
downloaded by your node automatically. Please upgrade.
We are still working on the request latency optimisations that we started on
Saturday. We have discovered that the median time taken by a typical CHK
request is vastly
Freenet 0.7 build 1195 is now available. Please upgrade ASAP. There are
several important changes in this build and recently, the first two of which
have caveats:
- Freenet nodes now accept fewer parallel requests. This is an attempt to
reduce the average time taken by a successful CHK fetch,
On Sat, Jan 10, 2009 at 4:58 PM, Matthew Toseland
wrote:
> A partial solution
> is to implement a progress screen when loading a page; this will be done in
> the near future. If you have expertise in Javascript, please contact us, we
> could really do with some help for the next stage.
You
Freenet 0.7 build 1195 is now available. Please upgrade ASAP. There are
several important changes in this build and recently, the first two of which
have caveats:
- Freenet nodes now accept fewer parallel requests. This is an attempt to
reduce the average time taken by a successful CHK fetch,
On Sat, Jan 10, 2009 at 4:58 PM, Matthew Toseland
t...@amphibian.dyndns.org wrote:
A partial solution
is to implement a progress screen when loading a page; this will be done in
the near future. If you have expertise in Javascript, please contact us, we
could really do with some help for the
On Wednesday 24 December 2008 18:34, bbackde at googlemail.com wrote:
> I still get this:
>
> * Probably a bug: please report: 2 peers forcibly disconnected due
> to not acknowledging packets.
> * Probably a bug: please report: 1 peers forcibly disconnected due
> to not acknowledging
On Wednesday 24 December 2008 18:34, bbac...@googlemail.com wrote:
I still get this:
* Probably a bug: please report: 2 peers forcibly disconnected due
to not acknowledging packets.
* Probably a bug: please report: 1 peers forcibly disconnected due
to not acknowledging packets.
This problem is resolved for me. Thanks!
On Wed, Dec 24, 2008 at 7:34 PM, wrote:
> I still get this:
>
>* Probably a bug: please report: 2 peers forcibly disconnected due
> to not acknowledging packets.
>* Probably a bug: please report: 1 peers forcibly disconnected due
> to not
Matthew Toseland wrote:
> Freenet 0.7 build 1194 is now available. Please upgrade, this will be
> mandatory on Friday. Some fairly substantial changes:
It looks like the infamous "# peers forcibly disconnected" bug is gone
in this release, thanks and congratulations! (I see far less package
Matthew Toseland wrote:
Freenet 0.7 build 1194 is now available. Please upgrade, this will be
mandatory on Friday. Some fairly substantial changes:
It looks like the infamous # peers forcibly disconnected bug is gone
in this release, thanks and congratulations! (I see far less package
handling
I still get this:
* Probably a bug: please report: 2 peers forcibly disconnected due
to not acknowledging packets.
* Probably a bug: please report: 1 peers forcibly disconnected due
to not acknowledging packets.
with
* Freenet 0.7 Build #1194 r24387
* Freenet-ext Build #26
Freenet 0.7 build 1194 is now available. Please upgrade, this will be
mandatory on Friday. Some fairly substantial changes:
- Fix a serious bug causing the packet sending loop to be very unfair to nodes
late on in the peers table.
- When reconnecting or rekeying, if the other side decides not to
Freenet 0.7 build 1194 is now available. Please upgrade, this will be
mandatory on Friday. Some fairly substantial changes:
- Fix a serious bug causing the packet sending loop to be very unfair to nodes
late on in the peers table.
- When reconnecting or rekeying, if the other side decides not to
Freenet 0.7 build 1193 is now available. Please upgrade. Changes:
- Significant changes to the old-opennet-peers mechanism, should make
reconnecting after downtime much quicker, nodes should get back to where they
were on the network more quickly even after long downtimes. This will only
really
Freenet 0.7 build 1193 is now available. Please upgrade. Changes:
- Significant changes to the old-opennet-peers mechanism, should make
reconnecting after downtime much quicker, nodes should get back to where they
were on the network more quickly even after long downtimes. This will only
really
Sorry for the belated changelogs ... Please upgrade!
1190:
- 1189 broke seednodes. Fixed in 1190.
1191:
- Fix startup failures due to problems with updater temp files. Delete the old
temp files.
1192:
- Fix a major unfairness bug in the packet sending scheduler code. This may
have caused some
bill
> From: toad at amphibian.dyndns.org
> To: devl at freenetproject.org; support at freenetproject.org
> Date: Sat, 6 Dec 2008 14:49:14 +
> Subject: [freenet-support] Freenet 0.7 build 1189
>
> Freenet 0.7 build 1189 is now available. Please upgrade, it will be manda
Freenet 0.7 build 1189 is now available. Please upgrade, it will be mandatory
on Tuesday. Changelog:
- Another new version of the connection setup protocol which hopefully will be
the last for some time, which should fix the current disconnections problems
by negotiating whether to reuse the
Freenet 0.7 build 1189 is now available. Please upgrade, it will be mandatory
on Tuesday. Changelog:
- Another new version of the connection setup protocol which hopefully will be
the last for some time, which should fix the current disconnections problems
by negotiating whether to reuse the
bill
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; support@freenetproject.org
Date: Sat, 6 Dec 2008 14:49:14 +
Subject: [freenet-support] Freenet 0.7 build 1189
Freenet 0.7 build 1189 is now available. Please upgrade, it will be mandatory
on Tuesday. Changelog:
- Another new
Freenet 0.7 build 1188 is now available, and will be mandatory on Saturday.
Please upgrade. The main change in this build is a change to the connection
setup code: Every hour or so we change the connection encryption key for
various reasons. Before 1188, we had tied this key to the
Freenet 0.7 build 1188 is now available, and will be mandatory on Saturday.
Please upgrade. The main change in this build is a change to the connection
setup code: Every hour or so we change the connection encryption key for
various reasons. Before 1188, we had tied this key to the
Freenet 0.7 build 1187 is now available. Please upgrade. Changes:
- Maybe fix a bug causing IP addresses to be lost for nodes, especially on
darknet.
- When the Bloom filter size is set to -1 (the default, meaning autodetect),
keep it as -1, so when we change the store size the bloom filter size
Freenet 0.7 build 1187 is now available. Please upgrade. Changes:
- Maybe fix a bug causing IP addresses to be lost for nodes, especially on
darknet.
- When the Bloom filter size is set to -1 (the default, meaning autodetect),
keep it as -1, so when we change the store size the bloom filter size
On Monday 01 December 2008 07:11, Ronald Wiplinger (Lists) wrote:
> How to upgrade?
>
> Automatic upgrade did not work.
> Now it does not even start anymore.
Please send me your wrapper.log. This will be in the directory you installed
Freenet to. Thanks.
>
> bye
>
> Ronald
>
>
> Matthew
On Mon, 01 Dec 2008 15:11:07 +0800
"Ronald Wiplinger (Lists)" wrote:
> How to upgrade?
On Windows:
Click My Computer, Browse to Freenet folder, double click on update.cmd
-or-
Start => (type) cmd [enter] => (type) cd c:\program files\freenet (or wherever
you installed Freenet)[enter] => (type)
How to upgrade?
Automatic upgrade did not work.
Now it does not even start anymore.
bye
Ronald
Matthew Toseland wrote:
> Freenet 0.7 build 1186 is now available. Please upgrade, it will be mandatory
> on Tuesday. Changes:
> - Fix a nasty race condition in the message handling code. Impact is
On Mon, 01 Dec 2008 15:11:07 +0800
Ronald Wiplinger (Lists) [EMAIL PROTECTED] wrote:
How to upgrade?
On Windows:
Click My Computer, Browse to Freenet folder, double click on update.cmd
-or-
Start = (type) cmd [enter] = (type) cd c:\program files\freenet (or wherever
you installed
On Monday 01 December 2008 07:11, Ronald Wiplinger (Lists) wrote:
How to upgrade?
Automatic upgrade did not work.
Now it does not even start anymore.
Please send me your wrapper.log. This will be in the directory you installed
Freenet to. Thanks.
bye
Ronald
Matthew Toseland
How to upgrade?
Automatic upgrade did not work.
Now it does not even start anymore.
bye
Ronald
Matthew Toseland wrote:
Freenet 0.7 build 1186 is now available. Please upgrade, it will be mandatory
on Tuesday. Changes:
- Fix a nasty race condition in the message handling code. Impact is
Freenet 0.7 build 1186 is now available. Please upgrade, it will be mandatory
on Tuesday. Changes:
- Fix a nasty race condition in the message handling code. Impact is uncertain
but could be large - it broke an update-over-mandatory between nodes on the
same computer in testing.
- Implement
Freenet 0.7 build 1186 is now available. Please upgrade, it will be mandatory
on Tuesday. Changes:
- Fix a nasty race condition in the message handling code. Impact is uncertain
but could be large - it broke an update-over-mandatory between nodes on the
same computer in testing.
- Implement
Freenet 0.7 build 1187 is now available. Mostly minor changes but one was
important for newly installed nodes:
- Maybe fix darknet peers losing their IP addresses (bug 2688). We were losing
IPs on connect and on rekeying (every hour!).
- Keep a -1 setting for the Bloom filter size as -1. New
On Thu, 27 Nov 2008 20:55:50 +, Matthew Toseland
wrote:
> Changes in 1185:
> - Maybe fix the bandwidth collapsing bug. When a connection stalled,
> this bug caused us to lose messages, resulting in finished requests
> not being removed, resulting in the node thinking it is more
> overloaded
On Thu, 27 Nov 2008 20:55:50 +, Matthew Toseland
[EMAIL PROTECTED] wrote:
Changes in 1185:
- Maybe fix the bandwidth collapsing bug. When a connection stalled,
this bug caused us to lose messages, resulting in finished requests
not being removed, resulting in the node thinking it is more
Freenet 0.7 build 1185 is now available. Please upgrade. This build will be
mandatory on Monday. If you have any problems updating please let us know,
include your wrapper.log, and update manually using the update scripts
(update.sh or update.cmd). If you discover any bugs please report them,
Freenet 0.7 build 1185 is now available. Please upgrade. This build will be
mandatory on Monday. If you have any problems updating please let us know,
include your wrapper.log, and update manually using the update scripts
(update.sh or update.cmd). If you discover any bugs please report them,
Freenet 0.7 build 1181 is now available. It will be mandatory on Sunday.
Please upgrade.
The main change in 1181 is a partial fix (workaround) to the download
corruption bug. All sites should now load without decompression errors and
without silent data corruption. However, we implement this
Freenet 0.7 build 1181 is now available. It will be mandatory on Sunday.
Please upgrade.
The main change in 1181 is a partial fix (workaround) to the download
corruption bug. All sites should now load without decompression errors and
without silent data corruption. However, we implement this
Freenet 0.7 build 1180 is now available. Please upgrade. This build, and the
associated freenet-ext.jar, fix two major bugs (in buckets and block padding)
which we believe to be related to the recent download/browsing problems (bug
2694). 1180 is mandatory on Thursday. Note that one or two
Freenet 0.7 build 1180 is now available. Please upgrade. This build, and the
associated freenet-ext.jar, fix two major bugs (in buckets and block padding)
which we believe to be related to the recent download/browsing problems (bug
2694). 1180 is mandatory on Thursday. Note that one or two
On Fri, 14 Nov 2008 18:21:50 -0500, Dennis Nezic
wrote:
> On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
> wrote:
>
> > Freenet 0.7 build 1178 is now available.
I spoke too soon. It works fine for an hour or two, but then, at least
for me, all communcation (net input/output) STOPS.
On Fri, 14 Nov 2008 18:21:50 -0500, Dennis Nezic
[EMAIL PROTECTED] wrote:
On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
[EMAIL PROTECTED] wrote:
Freenet 0.7 build 1178 is now available.
I spoke too soon. It works fine for an hour or two, but then, at least
for me, all communcation
On Friday 14 November 2008 23:21, Dennis Nezic wrote:
> On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
> wrote:
>
> > Freenet 0.7 build 1178 is now available.
>
> Wow! What a difference. 1178 is like a totally different program, with
> respect to both cpu and memory usage. THANK YOU! It's
On Friday 14 November 2008 17:40, Dennis Nezic wrote:
> On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland
> wrote:
>
> > Freenet 0.7 build 1175 is now available. Please upgrade. Changes:
> > - Handle the "Packet X sent Yms ago and still not acked" bug better.
> > Don't complain in the log
Freenet 0.7 build 1178 is now available. Please upgrade. Sorry I accidentally
released 1176, then had some bugfixes in 1177 and 1178. Anyway, the main
changes relative to 1175:
- Try to prevent both sides of a connection attempting to rekey at the same
time, by having the receiver start 2.5
On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
wrote:
> Freenet 0.7 build 1178 is now available.
Wow! What a difference. 1178 is like a totally different program, with
respect to both cpu and memory usage. THANK YOU! It's no longer peaking
for minutes at a time. It's consistently low. My
On Fri, 14 Nov 2008 19:52:46 +, Matthew Toseland
wrote:
> It still has 100% CPU most of the time then? Apparently resulting
> from Freenet itself rather than downloads etc?
Well, it's not /so/ serious that it stays at 100% all the time. It
jumps up for a few minutes, then calms down to
On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland
wrote:
> Freenet 0.7 build 1175 is now available. Please upgrade. Changes:
> - Handle the "Packet X sent Yms ago and still not acked" bug better.
> Don't complain in the log until 10 minutes, then disconnect from the
> peer and log the fact.
On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland
[EMAIL PROTECTED] wrote:
Freenet 0.7 build 1175 is now available. Please upgrade. Changes:
- Handle the Packet X sent Yms ago and still not acked bug better.
Don't complain in the log until 10 minutes, then disconnect from the
peer and log
Freenet 0.7 build 1178 is now available. Please upgrade. Sorry I accidentally
released 1176, then had some bugfixes in 1177 and 1178. Anyway, the main
changes relative to 1175:
- Try to prevent both sides of a connection attempting to rekey at the same
time, by having the receiver start 2.5
On Friday 14 November 2008 17:40, Dennis Nezic wrote:
On Thu, 13 Nov 2008 18:16:55 +, Matthew Toseland
[EMAIL PROTECTED] wrote:
Freenet 0.7 build 1175 is now available. Please upgrade. Changes:
- Handle the Packet X sent Yms ago and still not acked bug better.
Don't complain in the
Please tell me, one way or the other, whether the problem is solved or whether
Freenet continues to use lots of CPU etc etc. Thanks.
On Friday 14 November 2008 19:52, Matthew Toseland wrote:
On Friday 14 November 2008 17:40, Dennis Nezic wrote:
On Thu, 13 Nov 2008 18:16:55 +, Matthew
On Fri, 14 Nov 2008 19:52:46 +, Matthew Toseland
[EMAIL PROTECTED] wrote:
It still has 100% CPU most of the time then? Apparently resulting
from Freenet itself rather than downloads etc?
Well, it's not /so/ serious that it stays at 100% all the time. It
jumps up for a few minutes, then
1 - 100 of 552 matches
Mail list logo
