[mythtv-users] Suspend not working if triggered by backend
dargllun at googlemail.com
Wed Jan 5 12:53:35 UTC 2011
On 05.01.2011 12:37, Jan Schneider wrote:
> I guess there must be more people out there using suspend + mythwelcome?
It seems that many people around here (especially the experts) use
distributed setups with the BE running 24/7.
> Does it work for you without problems? If yes, how does your setup
> differ from mine? Don't you have to unload drivers and thus stop the
> backend for suspend to work?
I do need to stop the backend, so that the DVB drivers for my Hauppauge
Nova PCI can be unloaded.
When I started out with mythtv, I had similar problems fighting my way
through the jungle of the existing MythTV shutdown/suspend
infrastructure. I also had serious issues with the built-in idle monitor
(0.22 timeframe). I finally reached a point where I chose to replace the
built-in complicated magic with external, but self-written complicated
The most central piece is a MythShutdown script which does what I want,
- program the timer for the next recording
- stop the backend
- stop LCDd and irw
- other magic required on my box such as unloading the network driver
and suspend the frontend
- suspend the machine
- bring up the above in reverse order
This script can be tested and tuned quite nicely until it works for you.
In addition, I have a global script called MythIdleMonitor running which
maintains an idle countdown which is reset upon several triggers (users
logged in, browser running, email client running, mythtv showing media,
remote buttons pressed...) Once the countown reaches zero, MythShutdown
Of the mythtv script hooks I only use the one to set the recording time,
so that mythshutdown -x works.
I found this more universal and mainable for my needs.
More information about the mythtv-users