I stumbled upon this issue while testing my changes to the scheduler.
I created a simple sequence file, with a single 1-second luminance capture, configured to store to /tmp/kstars_tests.
I observed that every time the sequence was executed, a capture would me made, and the previous capture would be immediately deleted.
Running KStars with a syscall filter gave:
See how "Light_006.fits" is getting deleted at the instant "Light_007.fits" is stored? I'm still looking for the part of the code that is doing the "unlink" on the last capture file.
This is annoying to me because (1) it proves that I did not run the test vectors I committed at the exact location their contents suggest and (2) I'd like to use /tmp as a generic location for automated tests. Any ideas on the reason? Thanks!