RyanJ

Members
  • Posts

    1
  • Joined

  • Last visited

RyanJ's Achievements

New User

New User (1/3)

  1. Hello all, Seems I've stumbled across a bug whereby using a config file seems to cause btsync to ignore changes to the device_name in that same config file. Take this config file for example: { "device_name" : "hostname", "listening_port" : 0, "storage_path" : "/root/.sync", "check_for_updates" : false, "use_upnp" : true, "download_limit" : 0, "upload_limit" : 0, "shared_folders" : [ { "secret" : "some_secret", "dir" : "/some/path", "use_relay_server" : true, "use_tracker" : true, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false } ] } If you run the btsync application as a daemon (I have tested this on Linux ARM with version 1.1.48 and 1.1.70 and a friend with Linux x64 version 1.1.48) pointed to that config file, the device name will show up correctly as "hostname" to other clients. However, if you change the device_name variable (let's say to "namehost"), then restart the application, it ignores the changed device_name and other clients will still see it as "hostname". Poking around, looking within /root/.sync, inside sync.dat is the old device name - it never gets changed. The workaround is to delete either the entire .sync folder, or at least just the sync.dat file so that the application regenerates it from the config file. I realize this is not a common use case, but given that I discovered it when I accidentally forgot to start btsync with the config file the first time, and having the device show up as "My Sync Device" for a while after, I got curious. Thanks! RyanJ