search

warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

Logfile Rotation #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Tracelog file (peerblock.log) should have a maximum size; after that size
is reached we should save aside a copy of the old one and rollover to a new
file.  When PeerBlock starts, we should also save aside the old file (or
some number thereof) in case it contains debugging-info we'd like to have
sent to us.

Original issue reported on code.google.com by peerbloc...@gmail.com on 13 Jul 2009 at 3:59

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 13 Jul 2009 at 4:03

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 24 Jul 2009 at 5:45

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 24 Jul 2009 at 5:50

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 24 Jul 2009 at 5:51

GoogleCodeExporter commented 9 years ago

Original comment by peerbloc...@gmail.com on 30 Jul 2009 at 6:18

GoogleCodeExporter commented 9 years ago 
Fixed in r113-r115 commits.  We're now treating peerblock.log as per the same 
rules
the user has configured to apply to history.db (i.e. Delete vs. Archive & 
Delete).

Original comment by peerbloc...@gmail.com on 25 Aug 2009 at 2:41