remo

Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Everything posted by remo

  1. remo
    Yes, 100% sure! Happens on all kinds of computers and since 1.3 doesn't get installed automatically, all of our computers are still on 1.2.91.. I guess I'll upgrade to 1.3 and increase the log size.
  2. remo
    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
  3. remo
    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?
  4. remo
    No, everything is writable in our environment.
  5. remo
    Same happened to us with 1.0.134 on different Windows systems. Please investigate this, we're looking for alternatives.. Luckily for btsync we can't seem to find any tool that offers what we need.
  6. remo
    We're having the same issues. A folder synced with three computers, one wasn't running for a while and when it came back online, it told the other twos to delete all the files they've added. It wasn't fatal, the files were still to be found in .SyncTrash but things like that are still terribly annoying.
  7. remo
    Same problem, had to install it manually. The script works nicely but most of the files disappear once you reboot the NAS (TS-412).