On 9/24/07, <b class="gmail_sendername">MartinG</b> <<a href="mailto:gronslet@gmail.com">gronslet@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi list!<br><br>I have a question regarding Mythwelcome.<br>The short version:<br><br><snip to make it even shorter ;-) ><br><br>Any help appreciated!<br></blockquote></div><br>Martin,<br><br>If I understand the situation correctly, to summarize:
<br>1) You have a BE (which may also be an FE) and a separate FE<br>2) Manual testing of alarm-script.sh on the BE is ok<br>3) You have configured MythWelcome on the FE<br>4) Attempts to let MythWelcome shutdown both the FE and the BE result in errors on the BE, including this snippet:
<br><br> Backend log reads (/var/log/mythtv/mythbackend.log):<br> 2007-09-23 12:24:05.858 I'm idle now... shutdown will occur in 180 seconds.<br> ...<br> 2007-09-23 12:26:45.077 20 secs left to system shutdown!
<br> 2007-09-23 12:26:55.091 10 secs left to system shutdown!<br><br> Broadcast message from root (Sun Sep 23 12:27:05 2007):<br><br> The system is going down for system halt NOW!<br> sh: /usr/bin/nvram-wakeup: No such file or directory
<br><br>Your problem appears to be that you overlooked setting up MythWelcome on the BE. I expect you'll find that when you run<br> # mythwelcome -s<br>on the BE that the setting for nvram-wakeup command is still /usr/bin/nvram-wakeup and needs to be changed to /home/mythtv/.mythtv/alarm-
script.sh. Don't forget you have two separate systems being shut down and each needs to be told how to do it.<br><br>While you're at it, consider what you want the system to do when it wakes up. As you have them currently configured, when the BE wakes up it won't shut down until someone runs mythfrontend (on either box) manually because:
<br> On the FE you have:<br> Automatically start: No<br> And on the BE you have:<br> Block shutdown before client connected: checked<br> (and since I suspect you didn't configure MythWelcome on it, the default for Automatically start: is NO, anyway)
<br><br>I set my system up to *not* "Block shutdown before client connected" because I have my system waking up to do recordings at all hours of the day and night and to run mythfilldatabase and I want it to go back to sleep without requiring my attention. If you tried going the other way and set "Automatically start" to yes, you're still stuck because it won't shut down while a front end session is running.
<br><br>HTH,<br>Craig.<br>