tomsam

Members
  • Content Count

    4
  • Joined

  • Last visited

About tomsam

  • Rank
    New User
  1. Hi, ok, yes, I have credentials, and setting the credentials in the config -as you proposed- is a workaround that solves this issue. Two things: 1) The setup with the credentials somewhere else had been working for months without any problems. The problems have started after the last update. 2) I guess most of the users don't like passwords stored in the clear somewhere in their filesystem. Is it likely that we will get an update for this soon? Thanks and regards, tomsam
  2. actually, after the last update on my Xubuntu 12.04 system, I get - an exclamation mark in the indicator symbol - an error message in the indicator (Communication error 401), - the option to open the web interface is disabled (but is running), - and if I try to restart, I keep getting the Error caught message: $ BitTorrent Sync forked to background. pid = 23114WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message... Has anything gone wrong with the last update?
  3. Hi all, does a Synology NAS (running btsync 1.2.82) spin down the drive(s) after a certain period of inactivity especially if only RO-Secrets are used? Is there an option (Synology or btsync) to only spin the drives up again, if there are incoming changes from remote? Regards, tomsam
  4. Hi all, recently, I tried to sync a file with a name similar to the following Screenshot - 02022014 - 10:32:03 AM.png from a Ubuntu 12.04 system (running btsync 1.2.82) to a Windows 7 Pro system (running btsync 1.2.82). The sync didn't start. I googled a little bit, and some users were talking about problems with special chars. Thus, I renamed the file to "Screenshot_02022014_10_32_03_AM.png" and the sync started and completed. Can anyone enlighten me a little bit on what the term "special chars" in this case is supposed to mean? Is there a list of characters that cannot be used? Does this depend on the target system (to be precise on the target file system, e.g. NTFS does not accept "/\*?<>|: in filenames, if I remember well)? In other words: What happens, if there is a filename with an illegal filename on the target system? Is there any kind of transformation applied to the filename, or are the files just stuck forever? In addition, I want to use btsync to synchronize my dad's "Own files" folders to a System R running a unix environment (PC->R only via an RO-secret, target filesystem ext2,ext3 or ext4). Will it be likely that I'll be getting problems with special characters (like Umlauts äöüß) in filenames that my father used on his Windows 7 system? Regards, tomsam PS R could be a NAS or simply a USB drive attached to a Pi.