Comment 2 for bug 803672

If you start syncdaemon once in a terminal, and then in another, the second instance, instead of dying, does this (many times, from different places, always the same exception):

Logged from file states.py, line 378
Traceback (most recent call last):
  File "C:\Python27\lib\logging\handlers.py", line 77, in emit
    if self.shouldRollover(record):
  File "C:\Users\ROBERTO\canonical\ubuntuone-client\ubuntuone\logger.py", line 101, in shouldRollover
    self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file
Logged from file states.py, line 448
Traceback (most recent call last):
  File "C:\Python27\lib\logging\handlers.py", line 77, in emit
    if self.shouldRollover(record):
  File "C:\Users\ROBERTO\canonical\ubuntuone-client\ubuntuone\logger.py", line 101, in shouldRollover
    self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file
Logged from file main.py, line 271
Traceback (most recent call last):
  File "C:\Python27\lib\logging\handlers.py", line 77, in emit
    if self.shouldRollover(record):
  File "C:\Users\ROBERTO\canonical\ubuntuone-client\ubuntuone\logger.py", line 101, in shouldRollover
    self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
ValueError: I/O operation on closed file