Write the Log file (also) with the Save button , or create an specific button

[GoogleCodeExporter]

Enhancement : Write the Log file (also) when the Save button is clicked ,
                or create an specific button .

Reason : I understand the Log file is only written when PB is closed , so ,

using the actual Save button to write the Log file (besides the Conf file),
or creating a button specific for this ,
would permit to examine the Log without exiting PB .

(my case is actually worst , as I can only start PB on PC boot = Issue 80)

Original issue reported on code.google.com by JRF...@gmail.com on 30 Sep 2009 at 1:01

[GoogleCodeExporter]

The peerblock.log logfile is actually written-to whenever we have something new 
to
log.  I regularly use a "tail" type program to monitor the contents of 
peerblock.log
while I'm testing out changes to it.  If the logfile ISN'T being written to 
during
regular operation, that's definitely a bug!

Please try opening peerblock.log with Notepad after you've started PeerBlock; it
should have all the startup stuff in there.  A line declaring that it's 
starting,
what version and OS rev you're running, a bunch of stuff as it loads the driver 
and
checks for updates, etc.  It should again log a bunch of stuff when you tell it 
to
check for updates, and when you exit PeerBlock it should write out a bunch more
stuff, ending with "Have a nice day!" . . . again this should all be happening 
live
however.

What program are you using to view this file while PeerBlock's running?  Maybe
there's an issue with the way that program's attempting to lock the file or
something?  The two programs I use most often are Notepad2 and Baretail, and I 
can
confirm that they are working without problem...

Original comment by peerbloc...@gmail.com on 30 Sep 2009 at 9:19

[GoogleCodeExporter]

Thanks for your attention and responses .
The PB Log is in fact working perfectly , you may 'burn' this issue .

I am embarrassed to confess I was deceived for the lack of entries in the Log ,
during many hours (when I was preparing the attachments for other Issue) ,

but from your explanation I forced an update , and confirmed the Log was written
immediately . Thanks again .

Original comment by JRF...@gmail.com on 2 Oct 2009 at 10:51

[GoogleCodeExporter]

Okay, great, thanks for confirming that!  Closing this bug.

Original comment by peerbloc...@gmail.com on 3 Oct 2009 at 6:07

• Changed state: Invalid