blackketter

I got a nice message from support engineer Dan: This almost did it, but I also needed to do a: sudo apt-get purge btsync first to finish the clean up.

Hi, I'm trying to install the btsync on Ubuntu 12.04 using the instructions here: http://help.getsync.com/hc/en-us/articles/207689576 I had previously installed the tuxpoldo packages and have removed them before trying to install your version, including removing the old /etc/btsync (and every other remnant of the previous install I can find.) I get the following error: dean@monkey:/etc$ sudo apt-get install btsync Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: btsync 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/5,020 kB of archives. After this operation, 9,828 kB of additional disk space will be used. Selecting previously unselected package btsync. (Reading database ... 1259275 files and directories currently installed.) Unpacking btsync (from .../btsync_2.3.7-2_i386.deb) ... Processing triggers for ureadahead ... Setting up btsync (2.3.7-2) ... chmod: cannot access `/etc/btsync/init_user_config.sh': No such file or directory dpkg: error processing btsync (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: btsync E: Sub-process /usr/bin/dpkg returned an error code (1) Any idea what's gone wrong? Thanks in advance!

Yes, that's it! That's some pretty strange behavior. I suppose I'll need another identity for the other machine.

Hi, I've got Sync running on my Mac and home Ubuntu machine. I've got a folder synced from the Mac to the linux box, using the read-only key (I double checked this is in fact the right key). Everything synced up just fine. Buuuut... I created a symlink on the Ubuntu machine in the synced folder, using "sudo ln -s". I expected this to be ignored by the local sync agent, or at worse some error would be thrown. What I see, though, is a new symlink created on the Mac in the folder that should be read-only! Is this expected behavior? If so, is there an option to make a folder really-really-read-only? Thanks in advance, Dean