* I. Ivanov <[email protected]> [01-31-19 22:34]: > > > It doesn't work over network (on different computers) because DT code > > checks for existence of PID: > > https://github.com/darktable-org/darktable/blob/master/src/common/database.c > > So I guess currently there's no guard against 2 darktables running on > > different PCs accessing the same database on network share. > > > Thank you, I don't know the code... but my understanding is that DT "can" > run if the database is on a network share and more than one DT can connect > to it simultaneously. > > In my opinion at least 2 possible directions exist > > 1. Preserve multi client (this can be risky if both clients work on the same > images) but at the same time opens a lot of possibilities - people > collaborating together. > > 2. Enforce single client (this is safer) but at the same time limits the > expansion.
dt already forces a single client on a single machine using locks on the db's but nfs/cifs/sshfs apparently do not honor those locks. so if you wish to store your db's on remote filesystems, YOU will have to enforce only one instance of dt accessing those db's. > I think each would appeal to some. > > Thank you everybody for sharing thoughts and experience! > > Regards, > > B > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected] -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
