From: Lisa Ridley ------------------------------------------------------ OK, question for the wiser gurus on the board. I've been using Spideroak to keep certain files synced between my Mac = Mini at home, my iMac at work and my MacBook Air. I moved to Spideroak = from Dropbox about 4 months ago b/c I was not happy with the change = Dropbox made to their TOS. I've been encoutering some intermittent, recurring problems with = Spideroak where certain files will get deleted for no apparent reason. = Last night I had two templates for a website I'm working on disappear = during the night (luckily I had pushed them to my git repo so they were = recoverable). Even restoring the files from my git repo doesn't = work...Spideroak just eventually deletes them. I have no idea why, and = I've filed bug reports with them repeatedly over this issue as I have = encountered it before. I'm toying with the idea of using rsync and lsyncd to keep files synced = between the computers, using my remote server instance as the file = store. I've used rsync before to mirror sites and backup files, but = I've never used lsyncd. Evidently it's a lightweight, event-driven = daemon that will kick off the syncing process on your client computer = when it detects a file change to the local file system. There's a = project on Github called lipsync that looks like it consists of cron = jobs to manage the syncing of files to / from the server / remote = client. What pitfalls do you foresee with this process? After reviewing the = process flow diagrams that the author of lipsync was kind enough to = place on Github with his bash scripts, it looks to me like the only = issue will be that all events appear to be driven from changes to the = files on a remote client. If you have a client you're trying to keep in = sync that has no local file changes, any changes pushed from another = client to the server won't be automatically pulled down. That's easy = enough to overcome though by kicking off a syncing script manually on = your local machine, provided you don't forget to kick it off. This will only be used by me (don't have to worry about multiple users = here), so I'm not overly concerned about conflict resolution. What other pitfalls can you think of that I'm missing?