> Jay Summet wrote: > > I have configured my FE/BE box to automatically shut down when idle and > wake itself up to make recordings. I was able to use mythshutdown for > the pre-shutdown check and actual shutdown, but had to roll my own > script to set the acpi wakeup time. (I'm running Ubuntu 8.4 which uses > /proc/acpi/alarm even though it has the newer kernel). Myth version is > the 0.21-fixes branch, up-to-date as of a month ago. > > > > Questions: > > 1) I have Mythwelcome start up automatically upon boot-up. It has a > feature to "start the frontend automatically" but only if it was NOT an > automatic wakeup. (i.e. if somebody pushes the power button, the > frontend is kicked off, but if the machine woke itself up to do an > automated recording, it does not.) This feature does not work for me, > in that no matter why the machine starts up, the front end is started up > (I eventually unchecked this box, and now my wife has to push a button > to start up the front end, even if she manually started the computer). > Is this because I'm not using mythshutdown to set the wakeup time? > > 1a) if so, how do I fix mythshutdown to work with /proc/acpi/alarm? (to > make matters worse, my custom script changes the time_t seconds to local > time, not UTC, before writing it to /proc/acpi/alarm). > > 2) Sometimes I forget to exit out of the front end, and this keeps the > system from shutting down. Is there a way to make the front end time-out > (after say, an hour of no input) and exit back to mythwelcome? > > 3) Any general hints for mythboxes that turn themselves off/on? > > Thanks, > Jay Whenever I setup ACPI control I follow this page... https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake ...and it worked as desired everytime until I used 8.10 when I had to follow this page... http://www.mythtv.org/wiki/ACPI_Wakeup ...as well I recall having the problem where it would open the frontend everytime instead of MythWelcome and I would also sometimes have it exit right out to the desktop instead of to MythWelcome. From memory the problem was related to how you told the system to start MythWelcome instead of MythFrontend. Check out the MythWelcome section of the first link that I provided and look for the "I don't have startmythtv.sh" subtitle. Are you starting MythWelcome in this way? If so then I am unsure why you get the frontend everytime. That said I usually have it open to MythWelcome everytime anyway. It gives you a nice summary about what is happening and all you have to do is click one button on the remote and you are in! If your system wakes up when it is supposed to then I don't think you have a problem with your method of setting the wakeup time. I am fairly sure there is no way to time out a frontend because I have often used a logged in frontend to hold a system on while I work on the server or perform downloads. This timer-out type of feature would have to be specially written if possible I believe. the only hints I can give you is to use the two links I included above unless you have a more specific question.