I have noticed that even with logging set to normal with verbosity set
to 1 we now seem to get quite a bit of logging information - here is an
extract:
10}
1138657c2fde526b - InsertReply <- tcp/207.96.1.41:19114
17cfdee0158125e1 - QueryRestarted -> tcp/150.243.170.1:3002
Connection Error: Freenet.ConnectTimedOutException
262b9c655812322b - HandshakeRequest -> tcp/128.250.38.81:19114
Rawmessage:
HandshakeReply
{Source=tcp/128.250.38.81:19114, Depth=1, Build=117, Revision=1.15,
UniqueID=262b9c655812322b, Version=1.2, HopsToLive=1}
262b9c655812322b - HandshakeReply <- tcp/128.250.38.81:19114
Setting handshake from tcp/128.250.38.81:19114
17cfdee0158125e1 - InsertRequest -> tcp/128.250.38.81:19114
Rawmessage:
HandshakeReply
{Source=tcp/12.18.109.3:19114, Depth=1, Build=117, Revision=1.14,
UniqueID=8ec9fa2acff9e18a, Version=1.2, HopsToLive=1}
8ec9fa2acff9e18a - HandshakeReply <- tcp/12.18.109.3:19114
Setting handshake from tcp/12.18.109.3:19114
17cfdee0158125e1 - QueryRestarted -> tcp/150.243.170.1:3002
I am concerned that these logs might grow to fill someone's hard-disk
faster than Freenet ever will. What is the best way to address this?
Ian.
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
