Am Freitag, 11. April 2008 17:20:10 schrieb Matthew Toseland:
> On Friday 11 April 2008 16:00, Guido Winkelmann wrote:
> > Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> >
> > I spoke too early. The wrapper.log looks like this now (see attachment).
> >
> > It looks like if this con
On Friday 11 April 2008 17:18, Guido Winkelmann wrote:
> Am Freitag, 11. April 2008 17:20:10 schrieb Matthew Toseland:
> > On Friday 11 April 2008 16:00, Guido Winkelmann wrote:
> > > Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> > >
> > > I spoke too early. The wrapper.log looks
Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> Am Freitag, 11. April 2008 04:18:01 schrieb Daniel Cheng:
> > It's rebuilding the database and it would take some time for large
> > datastore. Do you have still any error message _before_ theses lines?
>
> The earliest messages in the
On Friday 11 April 2008 16:00, Guido Winkelmann wrote:
> Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> > Am Freitag, 11. April 2008 04:18:01 schrieb Daniel Cheng:
> > > It's rebuilding the database and it would take some time for large
> > > datastore. Do you have still any error
Am Freitag, 11. April 2008 04:18:01 schrieb Daniel Cheng:
> On Fri, Apr 11, 2008 at 10:07 AM, guido wrote:
> > After one of these updates (probably 1135), my node has restarted. That
> > was yesterday at about 7 am, but I can't say for sure, because the point
> > when this happened is no longer in
On Fri, Apr 11, 2008 at 10:07 AM, guido wrote:
> After one of these updates (probably 1135), my node has restarted. That was
> yesterday at about 7 am, but I can't say for sure, because the point when
> this happened is no longer in the logs. It's close to 24 hours later now, and
> it still has
On Friday 11 April 2008 17:18, Guido Winkelmann wrote:
> Am Freitag, 11. April 2008 17:20:10 schrieb Matthew Toseland:
> > On Friday 11 April 2008 16:00, Guido Winkelmann wrote:
> > > Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> > >
> > > I spoke too early. The wrapper.log looks
Am Freitag, 11. April 2008 17:20:10 schrieb Matthew Toseland:
> On Friday 11 April 2008 16:00, Guido Winkelmann wrote:
> > Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> >
> > I spoke too early. The wrapper.log looks like this now (see attachment).
> >
> > It looks like if this con
On Friday 11 April 2008 16:00, Guido Winkelmann wrote:
> Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> > Am Freitag, 11. April 2008 04:18:01 schrieb Daniel Cheng:
> > > It's rebuilding the database and it would take some time for large
> > > datastore. Do you have still any error
Am Freitag, 11. April 2008 15:19:57 schrieb Guido Winkelmann:
> Am Freitag, 11. April 2008 04:18:01 schrieb Daniel Cheng:
> > It's rebuilding the database and it would take some time for large
> > datastore. Do you have still any error message _before_ theses lines?
>
> The earliest messages in the
Am Freitag, 11. April 2008 04:18:01 schrieb Daniel Cheng:
> On Fri, Apr 11, 2008 at 10:07 AM, guido <[EMAIL PROTECTED]> wrote:
> > After one of these updates (probably 1135), my node has restarted. That
> > was yesterday at about 7 am, but I can't say for sure, because the point
> > when this happe
After one of these updates (probably 1135), my node has restarted. That was
yesterday at about 7 am, but I can't say for sure, because the point when
this happened is no longer in the logs. It's close to 24 hours later now, and
it still hasn't finished restarting.
The wrapper.log is full with l
On Fri, Apr 11, 2008 at 10:07 AM, guido <[EMAIL PROTECTED]> wrote:
> After one of these updates (probably 1135), my node has restarted. That was
> yesterday at about 7 am, but I can't say for sure, because the point when
> this happened is no longer in the logs. It's close to 24 hours later now,
After one of these updates (probably 1135), my node has restarted. That was
yesterday at about 7 am, but I can't say for sure, because the point when
this happened is no longer in the logs. It's close to 24 hours later now, and
it still hasn't finished restarting.
The wrapper.log is full with l
1137 just has an extra check to make sure the segfault doesn't happen even in
the case of a corrupt or malicious splitfile. Upgrade!
On Thursday 10 April 2008 16:50, Matthew Toseland wrote:
> Freenet 0.7 build 1136 is now available. Please upgrade. I forgot to
announce
> 1135; a big part of 113
Freenet 0.7 build 1136 is now available. Please upgrade. I forgot to announce
1135; a big part of 1136 is fixing bugs in 1135. Apologies for the recent
node crashes...
Changes:
1135:
- Increase the redundancy on splitfiles from 150% to 200%. Your node only
needs to download 100% of this to compl
1137 just has an extra check to make sure the segfault doesn't happen even in
the case of a corrupt or malicious splitfile. Upgrade!
On Thursday 10 April 2008 16:50, Matthew Toseland wrote:
> Freenet 0.7 build 1136 is now available. Please upgrade. I forgot to
announce
> 1135; a big part of 113
Freenet 0.7 build 1136 is now available. Please upgrade. I forgot to announce
1135; a big part of 1136 is fixing bugs in 1135. Apologies for the recent
node crashes...
Changes:
1135:
- Increase the redundancy on splitfiles from 150% to 200%. Your node only
needs to download 100% of this to compl
18 matches
Mail list logo
