Comment 9 for bug 1103193

I confirm that using dropbox, hamster.db is synced to the cloud immediately whenever it changes. If dropbox uses the same inotify events as u1 (as comment #4 suggests), it interprets the events differently.

However, syncing hamster.db between two computers is still not working properly:

If the user is logged into two computers at a time, and makes a change on computer A, dropbox will sync this change to computer B. However, since on B there's "hamster-service" keeping its copy of hamster.db open, it will not detect the change (unless it closes the file, which only happens at logout).
hence, if the user goes back to machine B and makes another change, this creates a file conflict with dropbox.

I wonder how people manage to sync their hamster data using u1 or dropbox? (Unless they're so very disciplined as to log out whenever they leave a computer. Suspend won't be enough.)