It'd be nice to get some notes on how to do this with /proc/acpi/alarm ... much better than nvram....
Why does mythwelcome need its own settings....
THe backend already knows how to turn of the machine, why do we have to specify it again in mythwelcome setup?
When using the described settings, the back-end no longer actually performs the shutdown anymore - instead it calls "mythshutdown --shutdown" and lets that program figure out what needs to be done in order to turn off. The "Command to shutdown" setting in Mythwelcome setup configures how mythshutdown turns off the machine once it has ensured that turning off now is permitted. Mythshutdown actually perform some extra checks to ensure it's a good idea to shutdown before turning off the computer (e.g. checks not within 15 minutes of a recording - that kind of thing). --Specto 14:00, 27 September 2008 (BST)
Timing out Mythfrontend?
It's still not clear to me -- say someone is watching a show with mythfrontend on a combined frontend/backend. Now say they fall asleep so they never exit to the mythwelcome screen. Is there some sort of timeout that can be specified for mythfrontend? Like say after 30 minutes of inactivity exit to mythwelcome? Or is that not necessary? The article is unclear on this point and it's the one thing that I am still confused about.
To answer the question above -- one possible reason is the frontend and backend aren't always on the same machine. --Cymen 15:01, 15 April 2008 (UTC)
Overlapping MythShutdown Info
Shouldn't the detail on MythShutdown be moved to the MythShutdown page? (http://www.mythtv.org/wiki/Mythshutdown)