redhead

The changes in the API from 1.4 to 2.0 are making it very difficult to adapt the same functionality. It might never get full functionality.

Look in /etc/alt/sources.list.d/ it is placed there as a seperate file. Sent from my GT-I9195 with Tapatalk

I was about to migrate a rather considerable number of users to btsync when they launched v. 2, we were willing to pay anywhere from 10$ to 100$ per user, but with the subscription model and linking of devices our trust and usage model, btsync was no longer an option, and we decided to go wit synching despite its immature state.

Since you're using the unofficial Debian package it is /usr/lib/btsync-common/btsync-core Sent from my GT-I9195 with Tapatalk

The theory in btsync is to supply the file with newest times tamp, but at the same time it checks to see if the file CRC check has changed, since you have an empty folder, I would expect it to begin resyncing from the other servers, if the contence in the .sync folder shows an earlier time stamp. Sent from my GT-I9195 with Tapatalk

> touch -t "200001010100" file And your file will be created with mtime set at year 2000 january 1st at 1am Sent from my GT-I9195 with Tapatalk

> apt-get remove btsync-common btsyncAnd its the server version you're running. Sent from my GT-I9195 with Tapatalk

The error you're getting in the end is because you have created a background zombie process by issuing ctrl +Z, you should either use Ctrl +C or let it finish.Use "fg" to bring it into a foreground process once again and terminate it correctly, or use the "kill -15" command on the process ID to send a correct terminate signal. The error you're seeing when removing the btsync package, is due to the /etc/init.d/btsync script missing a linux standard base compliant (another description) if you don't want to alter the script before removing the package, use the [--force] flag to dpkg. IE: > dpkg --force-all --remove btsync > dpkg --force-all --remove btsync-common