SocketReader ver 0.2.3 released

*** PLEASE READ THE CHANGELOG *** A new option --newline has been introduced. If this option is given, a "\n" (newline) character will be appended to each message written to a file. This was the standard behavior of socketReader until version 0.2.2 (beta). NOTE: In order to keep the behavior of socketReader 0.2.2, you _must_ give the option --newline from now on! Otherwise no newline character will be appended to messages written to file. There is also a known bug regarding access to the log file. When under heavy load, socketReader might not write complete log messages to the file on rare occasions, although the Python docs state the logging module to be thread safe. Wrapping this operation by using threading.Lock() yielded the same result, so I suspect the bug to be there.