Am Donnerstag, 6. März 2014, 16:46:04 schrieb Patrick Shanahan: > * Patrick Shanahan <p...@opensuse.org> [03-06-14 16:38]: > > * Tobias Ellinghaus <h...@gmx.de> [03-06-14 16:11]: > > > Am Donnerstag, 6. März 2014, 21:19:20 schrieb Dave: > > > > Thanks. > > > > I ran pkill darktable first to be sure and also ran fuser library.db > > > > to see > > > > if a process was accessing the database. > > > > > > And it still didn't want to start? That is strange, since the lock file > > > contains the PID of the process that locked the database, and when > > > darktable finds such a file on startup it checks if there is a process > > > with that PID. Granted, it doesn't check if it is really a darktable > > > process or just some random one which got the same PID by accident. > > > That would be a strange coincidence though. > > > > I believe you have read something into his post. As I understand, he ran > > pkill and fuser to determine that their actually was no darktable instance > > to preclude possible corruption of the library database. > > > > If, as you allude, darktable compares it's pid to that contained in the > > lock file and is supposed "make it's own correction", I am witness that > > that does not always happen as I have had to remove the lock in able to > > start darktable and istr that I started darktable from the cl and saw an > > error msg announcing the existing lock file. > > Just tested and darktable did remove and replace the existing lock file, > but I have had it fail in this recently.
Interesting. I crash darktable at least a dozen times a day (sometimes on purpose, sometimes by accident) while developing. And I never had that happen. It might very well be a bug. That's why I asked. Maybe I should add the command that has the old PID to the message to help debug it. Tobias
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
