I'm looking to find out where in the FS the "Shutdown/Wakeup Options" are stored. Currently, one can only have a max "Idle Timeout" of 1200 sec when setting this by the mythtv-setup (general options>fifth screen). I'd like to increase it to 1 hours (3600 sec) and am wondering if I can do so by editing a file.

Thanks all!

_________________
Retired KM user (R4 - R6.04); friend to LH users.

Probably in the database like everything else. Try: and search through the output.

sorry to answer the question with another! but why do you want that? i set it to 60 seconds when most people use 10 seconds! my understanding of the use of mythwelcome is that you exit to it when you want end the frontend. the machine goes idle, and then shuts down after the given amount of seconds. if you want to keep the machine on, just don't exit the frontend. if you go into mythwelcome, it is because you intend to shutdown (and have the machine wakeup appropriately).

are you thinking of this because sometimes you leave the machine on doing nothing, but you're not sure if you want to shut it down or will start watching something again soon?

note that once the machine woke up to record and finished recording, it'll go to mythwelcome. if you set the idle timeout to an hour, it'll stay up for an hour after each recording. but maybe that's what you want. maybe you watch the shows within an hour after a recording is over.. (i don't mind the machine shutting down, and then restarting it to watch the show, since i'm never sure when i'll watch the show )

anyway.. sorry, there are no answers in my "reply" i actually never looked into how to do that. but i was curious as to why you wanted that to begin with.

It's a fair question and what you said made a lot of sense. Chauk it up to me just learning about this feature and not fully understanding it.

I do want an additional buffer of time between shows now (the so-called "max wait for recordings" setting). I took at look at my 2 week schedule and have 2-4 h gaps between shows in some cases. Tweaking the idle time wouldn't help that much, but tweaking the time between would; I'd like to double the current max of 2 h to 4 h. Otherwise there are cases where it'll boot up, capture, go down and repeat in the same day which I'd like to avoid.

_________________
Retired KM user (R4 - R6.04); friend to LH users.

4 hours x 250W = 1kWh = 1kg C02 and 20c

It's a bit off topic but my Kill-A-Watt shows 122 W idle, so your math becomes 4 h x 122 = 0.49 kWh = 0.5 kg CO2. I don't understand the 20c

Plus, what your not factoring in is that the 4 h would be the max it would wait. Anyway, I'm still looking for the answer to the question.

_________________
Retired KM user (R4 - R6.04); friend to LH users.

I recently bought a new fridge.. I bet you wonder what this has to do with mythtv!!!!

The fridge had a sticker on it that gave how much money it costs per year, energy-wise. And the fine print below said:

Based on a 2001 US Goverment national average cost of 8.29c per kWh for electricity. Your actual operating cost will vary depending on your local utility rates and your use of the product. (i.e. maybe Greg's local rates are 20c per kWh)

Based on that, we have, on average: 0.5 kWh is about 4.15c


I only record one show a day, three times a week. So my machine goes on once to record, sleeps, then I turn it on to watch, and turn it off. Sometimes, I turn it on to watch a movie off my external harddrive. So I never looked into how to make that interval of time larger than 15 minutes.

Btw, sorry I'm not helpful on issues I didn't need to look into Too many things to do, and too little time... The usual story..

All I was trying to say is that there is a carbon cost and a financial cost to having your computer stay up 4 hours when it could shut itself down and then boot up again for the next recording. I realise that the energy costs and power usage are going to vary from person to person, system to system, that wasnt the point I was trying to make. Having said that, the command I gave you should list all of the settings in the database. A command like this can then change the settings: