Hi All:<br><br><div class="gmail_quote">On Fri, Nov 19, 2010 at 8:02 PM, Greg Oliver <span dir="ltr"><<a href="mailto:oliver.greg@gmail.com">oliver.greg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Nov 19, 2010 at 11:56 AM, Raymond Wagner <<a href="mailto:raymond@wagnerrp.com">raymond@wagnerrp.com</a>> wrote:<br>
> On 11/19/2010 11:44, Michael Papet wrote:<br>
>><br>
>> I am thinking the issue might be buried in an acpid, but the power button<br>
>> routine is dead simple.<br>
<br>
</div>If you are using *buntu, you can thank them for their (not<br>
so)wonderful attempt at an init system called upstart. I filed 2 bugs<br>
(both 10.04/10) about it.</blockquote><div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8">If you are running Ubuntu, could you please try applying this patch to the upstart job:</div><div>
<br></div><div><div>=== modified file 'debian/mythtv-backend.upstart'</div><div>--- debian/mythtv-backend.upstart<span class="Apple-tab-span" style="white-space:pre">        </span>2010-11-15 04:08:46 +0000</div><div>+++ debian/mythtv-backend.upstart<span class="Apple-tab-span" style="white-space:pre">        </span>2010-11-20 19:52:17 +0000</div>
<div>@@ -4,7 +4,7 @@</div><div> author "Mario Limonciello <<a href="mailto:superm1@ubuntu.com">superm1@ubuntu.com</a>>"</div><div> </div><div> start on (local-filesystems and net-device-up IFACE=lo and started udev-finish)</div>
<div>-stop on starting shutdown</div><div>+stop on runlevel [016]</div><div> </div><div> #expect fork</div><div> respawn</div></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It is one of the reasons I lost data and<br>
migrated away from them. There will still be daemons writing to disk<br>
with it just turns off. Pretty dismal.. I sure hope the up and<br>
coming systemd does not pull this crap to shave a couple seconds off<br>
of startup/shutdown times..<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div>I suspect this is actually just caused by some incorrect lines in some of the upstart jobs, not a characteristic problem of upstart itself. </div></div>