To see how well the tools work with some of the different types of files that are available on a Linux machine, I created a linux-fs-test directory tree which initially contains an empty dir2 and a dir1 with the following contents. To start, I first made sure that dir1 and dir2 were exact copies of each other and fully synced.
#Sync folders pro vs dirsync software#
I also created testfile.txt, a four-line file which I edited on each clone to see how the syncing software handles conflicts. I created a df1.txt file that contains today’s date and used it to see how the syncing software handles the case when the modification time of a file on both clones has changed but the file contents are identical. For a simple test of how the programs handle files that have been edited on both clones, I created a conflict-test directory that contains dir1 and dir2 as directories to sync. Here’s a hands-on look at two tools designed to accomplish that task: DirSync Pro and Unison.Īn up-front disclaimer: I use Unison for personal data syncing, but I will avoid any bias toward it in this article.īoth of these tools allow you to set up a configuration targeting two directories and have the contents of those directories recursively synchronized.
With bidirectional filesystem syncing tools, there is no primary filesystem - you just tell the tool to make sure both target directories, or clones, are identical.
Sometimes, however, you want to sync in the reverse direction. Everyone knows and loves rsync, the command that lets you clone a directory tree to another disk or system with the ability to keep the clone fresh in an incremental and bandwidth-efficient manner.
0 kommentar(er)
