<br><br><div class="gmail_quote">On Thu, May 13, 2010 at 11:33 AM, Graham Cobb <span dir="ltr"><<a href="mailto:g%2B770@cobb.uk.net">g+770@cobb.uk.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Thursday 13 May 2010 00:27:21 Faheem Pervez wrote:<br>
> On 5/13/10, Graham Cobb <<a href="mailto:g%2B770@cobb.uk.net">g+770@cobb.uk.net</a>> wrote:<br>
> > Faheem, what were you using as the start condition for your upstart<br>
> > script? I<br>
> > would have assumed that if it were anything after "start on started dbus"<br>
> > then the waitdbus would be unnecessary.<br>
><br>
</div><div class="im">> I was using:<br>
> "start on started dbus<br>
> stop on stopping dbus<br>
> stop on stopped fmtx"<br>
<br>
</div>Thanks Faheem. From your experience, it seems that "start on started dbus" is<br>
not good enough to know that dbus really is available so we should all get<br>
into the habit of adding the following into upstart scripts that need dbus<br>
(or which need run-standalone.sh), to avoid obscure race conditions:<br>
<div class="im"><br>
pre-start script<br>
/usr/sbin/waitdbus system<br>
end script<br></div></blockquote><div><br>I found that if I use :<br> start on started hildon-desktop<br><br>as starting condition, I don't need to put the pre-start script<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
<br>
</div><font color="#888888">Graham<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
maemo-developers mailing list<br>
<a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
</div></div></blockquote></div><br>