remo

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by remo

  1. The process has the same PID, unlikely it gets restarted. I can reproduce this behaviour on all computers we're using! sync.log is reset after about 10MB / 15minutes of data.

     

    I've had a closer look with process monitor, seems like there are two calls which might cause this issue. One is definitely coming from btsync where sync.log.old is created, but there's another one from svchost.exe. Not sure why the service process does that though..

     

    UPDATE: Couldn't upload my export of process monitor, you can find it here http://www.mesch.ch/sync.log

    post-25372-0-21313500-1396257226_thumb.p

  2. We are having issues with files being overwritten by older versions. No need to say that this is annoying. I told my guys to enable the debug log, but unfortunately, debug.log only contains FFFF and sync.log doesn't show us enough.

     

    Once we realize that a file has been overwritten, it's long gone from the sync.log. It looks like only the last 10-15 minutes are kept in the log file. While this might be nice to avoid a full harddisk, it's a bit tricky for us to get more information about the actual problem.

     

    All clients are currently using version 1.2.91 on Windows and one client runs on an ARM Linux NAS.

    Any ideas on how to catch more data in sync.log?