On Wed, Aug 6, 2014 at 2:11 AM, Baruch Burstein <[email protected]> wrote:
> On Fri, Aug 1, 2014 at 4:15 PM, Richard Hipp <[email protected]> wrote: > >> I don't know how closely a DropBox folder follows correct (published) >> filesystem semantics. If DropBox is doing some no-standard things, then it >> might be possible to corrupt the repository if it lives in a DropBox >> folder. I just don't know. >> >> The above is how Fossil is *designed* to work. Can you get it to also >> work using your DropBox approach? Maybe. It will require some >> experimentation, I suppose, to determine whether or not DropBox is pulling >> any dirty tricks that get the underlying SQLite storage engine confused. >> Perhaps others on this list can give a better answer. >> > > To the best of my knowledge, Dropbox is not a "virtual" filesystem. It is > a regular folder in the regular filesystem that is managed by the OS. The > only "special" thing about it is that Dropbox registers with the OS to be > notified of changes to this folder, and then syncs these changes, using > regular file read/write mechanisms supplied by the filesystem/OS. > > If some other process (like Dropbox) writes to an SQLite database file, or to an SQLite journal file, while SQLite is also using that file, that can lead to severe problems. I think that is the point. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
