On 2 Apr 2005, at 1:03 PM, David Engel wrote:
If a recording ends at 3am and mythfilldatabase runs a 4am, that is not when "mythfilldatabase runs the next day".
My mistake -- it's a random time between 4 and 28 hours, then, not a random time between 0 and 24 hours. I fail to see that as a significant improvement.
It makes perfect sense because mythfilldatabase is where any database housekeeping is done.
If it's an integral part of the housekeeping process, why is it included in a separate binary and run as frequently or infrequently as the user specifies? That is necessary for filling the database, where the procedure may involve custom jobs in the data grabbing, but not for normal mythbackend housekeeping.
"completes successfully" is a misnomer. That code runs when a recording is stopped for any reason and includes the cases where the user manually stops or deletes a recording while it is still in progress.
Okay, I had assumed "prematurestop" in the code meant "prematurely stopped", not "stopped due to error". Does Myth know when a recording is truly actually finished, then? Is mythcommflag initiated from another place, or does it get triggered if a user stops a recording in the middle?
Stopping or deleting prematurely are specific cases the reactivation logic is meant to handle.
Can someone provide a use case for reactivation? I just can't imagine choosing to delete a recording, and then wanting to start it again, and not caring that I missed some in the middle.
- Jeremiah
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
