Menu
▾
▴
#72 [4.0] Logging gone bad
open
nobody
None
5
2007-05-20
2007-05-20
No
Version: 4.0
OS: Windows XP
This problem leads back to the fact that I adjusted some settings that had to do with connections.
The Tribler log file got filled up to 1.5GB of "Too many connections" messages.
This obviously caused Tribler to freeze and Windows to run terribly slow and start to whine about disk space.
Basically, this is a feature request for a better logging class and some settings (max. log size, etc.) but since the problem is already in the release and it can occur without the user knowing it, I file it as a bug.
Logged In: YES
user_id=1750671
Originator: YES
In addition, Rick told me Python has excellent logging classes build in and he suggest using them.
Logged In: YES
user_id=216477
Originator: NO
Please show more detail, and next time, please comment on non-public release candidates directly to the tribler team (via email or a Trac ticket). This tracker should be used for bugs in public releases only.