* Owen Mays [12-21-19 23:33]:
> Thanks for the suggestions everyone. One final clarification/question: if I
> go with the "look for updated xmp files" option, does that mean I will need
> to import images once on each machine? And then once they're imported into
> the (local) library, then darktab
Thanks for the suggestions everyone. One final clarification/question: if I
go with the "look for updated xmp files" option, does that mean I will need
to import images once on each machine? And then once they're imported into
the (local) library, then darktable will watch for changes to the xmp fi
Hi Owen,
On 14.12.19 19:02, Owen Mays wrote:
1) Why go to the trouble of adding hostname to PID in the lock file, why
not just check for existence of the lock file and treat that as evidence
that the database is open? It looks like many lines of code have been
written in database.c dedicated
Hello Owen,
On Sat, Dec 14, 2019 at 7:02 PM Owen Mays wrote:
>
> 2) Since sharing the library is not recommended, is there a recommended
> way to have one computer be aware of edits made on/by another computer? The
> problem I'm trying to solve is: my photos live on my laptop and are usually
> i
9 PM Bruce Williams wrote:
>
> > Owen,
> > Have you looked at using the "local copies" feature?
> > That might be a safer alternative.
> > Just a thought.
> > Cheers,
> > Bruce Williams.
> >
> > -- Forwarded message --
thought.
> Cheers,
> Bruce Williams.
>
> -- Forwarded message -----
> From: Owen Mays
> Date: Sun., 15 Dec. 2019, 05:03
> Subject: Re: [darktable-dev] Database lock file seems too lenient
> To: Sturm Flut
> Cc:
>
>
> Hi Simon,
>
> Thanks for
Hi Simon,
Thanks for the response. I have a couple follow-up questions:
1) Why go to the trouble of adding hostname to PID in the lock file, why
not just check for existence of the lock file and treat that as evidence
that the database is open? It looks like many lines of code have been
written i
Hi Owen,
the locking mechanism could probably be extended to also include the
hostname in the lockfile.
The problem with putting SQLite databases on a network share is that
it's discouraged by SQLite [1] to begin with because too many things can
go wrong. If darktable's locking mechanism fai
