Le 17/09/2015 04:55, Patrick Shanahan a écrit : > >> To me, either DT of something else is writing to the photo file, am I in >> the right direction? > Only you can know about something writing to the raw/origianl, but it is > not dt. The right direction would be away from dt.
There are ways to monitor changes to files if you can use the command line. This might help you: http://serverfault.com/questions/320716/find-out-which-process-is-changing-a-file Alternative: If you suspect a particular program, you can get hints with strace. Let's say your complete path to directory is /somepath/. Do: strace -f darktable 2>&1 | grep /somepath/ It will show something like this (using darktable 1.6.8): stat("/somepath", {st_mode=S_IFDIR|0775, st_size=32768, ...}) = 0 [pid 11026] access("/somepath/somefile.jpg", F_OK) = 0 [pid 11026] stat("/somepath/somefile.jpg", {st_mode=S_IFREG|0664, st_size=203659, ...}) = 0 [pid 11026] access("/somepath/somefile.jpg", F_OK) = 0 [pid 11026] stat("/somepath/somefile.jpg", {st_mode=S_IFREG|0664, st_size=203659, ...}) = 0 [pid 11026] open("/somepath/somefile.jpg", O_RDONLY) = 12 [pid 11026] open("/somepath/somefile.jpg", O_RDONLY) = 12 [pid 11026] access("/somepath/somefile.jpg", F_OK <unfinished ...> [pid 11026] open("/somepath/somefile.jpg", O_RDONLY <unfinished ...> [pid 11026] access("/somepath/somefile.jpg", F_OK) = 0 [pid 11026] open("/somepath/somefile.jpg", O_RDONLY) = 12 [pid 11034] access("/somepath/somefile.jpg", F_OK <unfinished ...> [pid 11034] stat("/somepath/somefile.jpg", <unfinished ...> [pid 11034] open("/somepath/somefile.jpg", O_RDONLY <unfinished ...> [pid 11034] open("/somepath/somefile.jpg", O_RDONLY) = 12 [pid 11034] access("/somepath/somefile.jpg", F_OK) = 0 [pid 11034] access("/somepath/somefile.jpg", F_OK) = 0 [pid 11026] access("/somepath/somefile.jpg", F_OK) = 0 [pid 11026] access("/somepath/somefile.jpg", F_OK) = 0 [pid 11026] stat("/somepath/somefile.jpg", {st_mode=S_IFREG|0664, st_size=203659, ...}) = 0 [pid 11026] access("/somepath/somefile_01.jpg.xmp", F_OK) = 0 [pid 11026] open("/somepath/somefile_01.jpg.xmp", O_RDONLY) = 12 [pid 11026] stat("/somepath/somefile_01.jpg.xmp", {st_mode=S_IFREG|0664, st_size=2552, ...}) = 0 [pid 11026] open("/somepath/somefile_01.jpg.xmp", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 12 This trace shows that darktable opens image file in read-only mode, and xmp files in read then write mode. Hope this helps you in finding what is changing your files. By the way, there might be other reasons (e.g. is the storage device reliable)? -- Stéphane Gourichon ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
