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 second computer, it just overwrites the lock file. It appears this is due to logic in the database.c file that checks whether the PID in the lockfile belongs to an active process. Because the lockfile was created by a process on another computer, darktable thinks the lockfile is stale and overwrites it. Is there a reason the lockfile is not more strict? Why go to the effort of checking the PID, why not assume the lockfile means a lock, and if it's stale, leave it to the user to resolve? I can create a bash script wrapper to launch darktable that will first check for the lockfile, but I'd like to understand the design decision. Thanks, Owen ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
