* Owen Mays [12-14-19 17:03]:
> Bruce,
>
> Thanks for the suggestion. Unfortunately it looks like that doesn't do what
> I'm looking for. Edits made on one computer don't show up on the other
> computer (I think it's because they are only sharing the photo files, not
> the library database).
>
>
I'm not at home right now, but if you are interested, I did a video on the
local copies function.
It's here if you want to have a squiz
https://youtu.be/UQEBP__ETDA
Cheers,
Bruce Williams.
-- Forwarded message -
From: Owen Mays
Date: Sun., 15 Dec. 2019, 09:00
Subject: Re: [da
Bruce,
Thanks for the suggestion. Unfortunately it looks like that doesn't do what
I'm looking for. Edits made on one computer don't show up on the other
computer (I think it's because they are only sharing the photo files, not
the library database).
Here's what I tried:
Mount remote disk over s
Owen,
Have you looked at using the "local copies" feature?
That might be a safer alternative.
Just a 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
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
Hello Darktable Devs,
First of all, thanks for a fantastic program!
I'm attempting to share a darktable library between two computers (using
the same network storage), and I'm concerned about accidentally corrupting
the database. Darktable creates a lock file, but when I launch darktable on
the s
