[mythtv-users] Commercial flagging, shutdowns & lost recordings

Matthew Carle matthew_carle at hotmail.com
Mon Jan 23 02:52:13 UTC 2006


This is a problem I noticed a while ago but it just happened to me again. It
seems like it would affect most people who use commercial flagging and have
their backend set to shutdown when inactive.

At the end of a recording, the system prepares to shutdown. Commercial
flagging starts but doesn't interrupt the shutdown process. I see this sort
of thing in the log:

2006-01-22 23:20:03.151 I'm idle now... shutdown will occur in 240 seconds.
2006-01-22 23:20:12.170 230 secs left to system shutdown!
2006-01-22 23:20:22.192 220 secs left to system shutdown!
2006-01-22 23:20:32.213 210 secs left to system shutdown!
2006-01-22 23:20:40.120 Starting Commercial Flagging for "Out of Sight"
recorded from channel 1015 at Sun Jan 22 20:24:00 2006.
2006-01-22 23:20:41.118 New DB connection, total: 1
2006-01-22 23:20:41.166 New DB connection, total: 2
2006-01-22 23:20:42.233 200 secs left to system shutdown!
2006-01-22 23:20:52.256 190 secs left to system shutdown!


When the countdown has finished, it appears to decide to wait for the
commercial flagging to finish. So more than an hour later, we get this:

2006-01-23 00:33:55.566 Finished, 5 break(s) found.
nvram-wakeup: Do NOT write into nvram. Wake Up time must be
nvram-wakeup: at least 10 minutes in the future.


There was actually a recording scheduled to start at about this time but it
shut down anyway. Additionally, because nvram-wakeup didn't write to the
bios, it won't wake up for any future recordings - you have to manually
power it up after one of these occurrences.  I have also had it do it a few
times while I was watching a recorded show. Does this happen to anyone else?
Any ideas on how to avoid it? Anyone know if it has been fixed in the CVS
version?

Thanks,
Matthew.


More information about the mythtv-users mailing list