[mythtv-users] Long time Mythwelcome bugs?

[Neil Cooper]

I am running a mythtv 0.24.1 system (combined backend and frontend) on a single box, and using mythwelcome.

The backend configuration has 'idle shutdown timeout' set to 60 seconds, and the 'command to set wakeup time' runs a script which in turn just echo's the $time parameter to /sys/class/rtc/rtc0/wakealarm.

 I never explicitly shutdown my mythbox, when I'm done with the frontend I just exit that to the mythwelcome screen so the box can turn itself off when it is idle.
 
There are only 3 ways my mythbox ever gets powered up:

1) by a wake-on-lan message (indirectly generated from my rather unconventional remote control setup).
2) pushing the power button on the front of the PC.
3) from a bios (ACPI) wakeup set by the 'wakealarm' described above.

I've noticed that in the mythwelcome menu there is an option to 'lock shutdown'. In my setup this has no effect. Even when mythwelcome shows 'MythTV is locked by a user' the idle timeout still shuts the box down.

I've also noticed that with the 'automatically start mythfrontend' option set in mythwelcome configuration, that the frontend is always started, even if the box is started from a bios (ACPI) wakeup just to record something. This means it will never automatically shutdown again unless I am around to manually exit the frontend.

Its worked this way since I have been using mythtv (so for every version since at least 3 years) and on 2 different hardware platforms so I dont think its my hardware. Are these known bugs or am I missing something?


Thanks!

Neil Cooper.