<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> I'll admit, I've only been suspending for a couple of days, and only testing<br>
> it in my office. If I start to see issues, I guess I'll need to kill the<br>
> frontend. Thanks for the heads up.<br>
<br>
</div>This is my experience too; if mythfrontend is running when the<br>
computer suspends, all sorts of things can go wrong when it resumes.<br>
<br>
I have the power button on my remote set to run a script that kills<br>
mythfrontend (I'm thinking of changing that to shut it down gracefully<br>
using the python bindings), suspends, and then starts mythfrontend<br>
again. I considered doing it all in /etc/pm/sleep.d, but it's easier<br>
from a simple script because it's running as the correct user.<br></blockquote><div><br></div><div>Just fired up my frontend after letting it sleep all night and sure enough it wouldn't wake properly. Sleeping worked great during all my short-term tests, but I never left it for an extended period before last night. I suspect that the iscsi connection didn't recover (I am connecting via gpxe in my NIC bios with DHCP to configure it). I wonder if there is a setting on my server to preserve the connection for a longer time.</div>
</div>