On 2/9/16, David Mason <dma...@ryerson.ca> wrote: > On 9 February 2016 at 15:48, Richard Hipp <d...@sqlite.org> wrote: > >> A Fossil repository is an SQLite database, and you shouldn't create >> links (symbolic or hard) to SQLite databases. >> > > Understood, but this is a very low-contention server. I'm really just > using symlinks here to demonstrate the problem. > > I'll try current tip a bit later (when I get a chance), but I really don't > understand how a file from last year works, and one from this year (built > with the same version of fossil, using almost identical script) doesn't. I > there anything besides capabilities and unix file permissions that can > affect permission to write to a fossil file? >
You also need write permission on the directory that holds the *.fossil file, in order to create the journals. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
