Need a guide...

[Fuzzy]

Originally Posted by EnterNoEscape

I've seen times when SageTV got in it's own way at completing that task even with a "clean" shutdown, but I agree. If it's possible to ensure that all pending writes are written, it is strongly preferred. I can say because I worked around some of that, there is up to a 128k window of unwritten data that might be dangling at any given moment. The exception would be when the database is being rebuilt/compacted, but there are safeguards for that situation. The write mode used for the database causes writes to be immediately committed to disk, so you're likely safe in regards to everything SageTV intended to write.

IF it is getting told to shut down, and not just killed.

[EnterNoEscape]

Originally Posted by Fuzzy

IF it is getting told to shut down, and not just killed.

Correct. Also, to clear up my first sentence, I've seen SageTV kill the file writer while it appeared to be trying to write out some final data.

[Fuzzy]

So, some more playing around, and I have a method that seems to work for stopping opendct properly when the docker is told to stop via 'docker stop'... However, it appears that unraid doesn't do docker stop when you choose stop from the webui (as far as I can tell). Still going to dig further into this later, but out of time on it for now. I'm wondering if things were working 'okay' before, but my testing was stopping from unraid, and that might be the problem.