SteveT
07-24-2007, 05:19 PM
I've been working on a tool to manage the Tivo's NoReRecord list (also known as the 28-day rule). I'm hoping you gurus can provide some details about how the TiVo performs its nightly "cleanup". Here are some facts I've gathered so far:
1) Entries in the mfs /Recording/NoReRecord list don't get auto-added to the to-do list.
2) CancelDate is part of the name of the entries in the NoReRecord list.
3) Entries drop off the NoReRecord list at night(?) when the CancelDate passes 30 days old. This occurs without a reboot or a phone call.
4) I cannot find any mention of NoReRecord in any of the /var/logs.
5) Simply changing the CancelDate on the object does NOT cause entries to drop off as expected. Apparently, some other value is also involved.
6) Changing CancelDate to a future date, then changing it back to the original date causes the entry to NOT drop off when expected.
7) These "touched" entries do drop off, but at least one day late.
8) Entries on my unsubbed Tivo are never dropped off (AFAICT).
I'd like to determine the logic used by the "cleanup" process, to see what I'm missing. Can anyone describe this process in detail? Can I capture the code being executed?
Any helpful advice appreciated.
1) Entries in the mfs /Recording/NoReRecord list don't get auto-added to the to-do list.
2) CancelDate is part of the name of the entries in the NoReRecord list.
3) Entries drop off the NoReRecord list at night(?) when the CancelDate passes 30 days old. This occurs without a reboot or a phone call.
4) I cannot find any mention of NoReRecord in any of the /var/logs.
5) Simply changing the CancelDate on the object does NOT cause entries to drop off as expected. Apparently, some other value is also involved.
6) Changing CancelDate to a future date, then changing it back to the original date causes the entry to NOT drop off when expected.
7) These "touched" entries do drop off, but at least one day late.
8) Entries on my unsubbed Tivo are never dropped off (AFAICT).
I'd like to determine the logic used by the "cleanup" process, to see what I'm missing. Can anyone describe this process in detail? Can I capture the code being executed?
Any helpful advice appreciated.