<div class="gmail_quote">On Mon, Aug 30, 2010 at 6:27 AM, Craig Huff <span dir="ltr"><<a href="mailto:huffcslists@gmail.com" target="_blank">huffcslists@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jerry,<br>
<br>
I have a MBE/FE + 2 remote FEs set up the way you discuss. The BE<br>
does not (AFAIK) need to have an FE configured on it to use<br>
MythWelcome/Shutdown. You _will_ need (even works through ssh tunnel<br>
x-forwarded) keyboard, mouse, and video to configure<br>
MythWelcome/Shutdown (unless you're better than me -- not hard -- and<br>
can do it with mysql commands).<br>
<br>
Here's what I do:<br>
<br>
A) BE runs MythWelcome on startup -- if using MythBuntu this is<br>
simple: See notes in /etc/mythtv/session-settings.<br>
B) BE runs with the appropriate options turned on in<br>
/proc/acpi/wakeup to allow ethernet wakeup to wake the system up. I<br>
had to experiment with the options displayed by "cat<br>
/proc/acpi/wakeup" to find the right one -- seems to be different on<br>
each MOBO. You might also need additional one(s) to enable waking via<br>
the RTC alarm so the BE will wake up to record shows. I use a startup<br>
script in /etc/init.d/XXXXX && /etc/rc*.d/SnnXXXXX to make sure this<br>
is set each startup and shutdown (probably a belt and suspenders<br>
approach, but it works).<br>
C) BE runs ethtool -s eth0 wol g to enable Wake-On-LAN (again using<br>
startup script)<br>
D) Configure MythWelcome from it's pop-up dialogs invoked with 1)<br>
"i-key" and 2) "F11" key<br>
E) Configure Shutdown from mythtv-settings<br>
<br>
Then configure (repeat for each separate remote FE):<br>
A) FE to run MythWelcome<br>
B) FE turns on options in /proc/acpi/wakeup<br>
C) FE runs ethtool -s eth0 wol g to enable Wake-On-LAN (handy for<br>
remote maintenance from the BE or any other ssh-enabled system).<br>
D) Configure MythWelcome (settings are defined per system so they<br>
can be different from one BE, BE/FE, FE to another)<br>
<br>
Don't need to repeat Shutdown config. One size fits all, so consider<br>
the settings in that light. I set shutdown delay long enough so a<br>
remote FE can use WOL to wake up the BE and have a chance to connect<br>
to mythbackend before it (the BE) decides it has waited long enough<br>
and shuts back down. You also have to tell the FE (again via<br>
mythtv-setup) to wake up the mysql server (same as the BE for me)<br>
often enough and long enough so it is still trying when the BE gets up<br>
to speed and 1) is listening on the ethernet, and 2) has<br>
mythbackend/mysql running for the FE to connect to.<br>
<br>
Also, think about how long it takes your BE to wake up and be ready to<br>
record and dial the wake up lead time in mythtv-settings with some<br>
safety margin.<br>
<br>
I use ext3 partitions for my disk, so occasionally it wants to fsck<br>
them on boot up. To prevent this from happening when it is booting up<br>
to record a show and delay the start of the recording I check to see<br>
if it is due soon and modify the end-of-recording-session shutdown to<br>
create the force-fsck flag file (don't remember it's name ATM) and do<br>
a shutdown -r instead of shutdown -h (or in my case hibernating) so it<br>
will come right back up, do the fsck, MythTV will time out again and<br>
shutdown for good. This requires changing the shutdown command (IIRC<br>
it's in _both_ mythtv-setup -- for mythbackend to use -- and in<br>
MythWelcome -- for mythwelcome to use) to invoke a script I wrote<br>
which checks the fsck status, amongst other things, and takes<br>
appropriate action.<br>
<br>
Wrote this up quick, so if something doesn't make sense or it doesn't<br>
work for you, post back and I'll take more time later.<br>
<br>
HTH,<br>
<font color="#888888"><br>
Craig.<br>
</font></blockquote></div><br><div>Craig,</div><div><br></div><div>That's great info, thanks. A couple of questions:</div><div><br></div><div>1. Is there any reason for running mythwelcome on the backend if it is a backend only, and not a combined BE/FE?</div>
<div>2. Does mythwelcome on the frontend just display "asleep" or something like that as the backend status when the backend is off and mythfrontend is not running?</div><div>3. It sounds like the "Enable Database Server Wakeup" setting on the frontend configuration is where you put the wake-on-lan command to wake up the backend. Just want to verify this is the case.</div>
<div>4. Is it possible, in general, to wake up a sleeping computer via a USB IR receiver? Oh wait, never mind this one - just found it on the wiki.</div><div><br></div><div>Thanks,</div><div>Jerry</div>