<br><br><div class="gmail_quote">2011/5/6 Rahul Sundaram <span dir="ltr"><<a href="mailto:metherid@gmail.com">metherid@gmail.com</a>></span><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 05/06/2011 03:07 PM, cornel panceac wrote:<br>
><br>
> 2011/5/6 Rahul Sundaram<br>
><br>
</div><div class="im">> On 05/06/2011 06:08 AM, John Mellor wrote:<br>
> ><br>
> > What can I look at to determine where in the boot sequence that the<br>
> > problem bottleneck is, and how do I do it?<br>
> ><br>
><br>
> systemd-analyze<br>
><br>
> <a href="http://0pointer.de/blog/projects/blame-game.html" target="_blank">http://0pointer.de/blog/projects/blame-game.html</a><br>
><br>
> mmm<br>
> if i remember things correctly, you can't see in *analyze that systemd<br>
> is waiting minutes for a device.<br>
<br>
</div>What makes you think that? If systemd is waiting for a few minutes on<br>
something, it should show up somewhere in the chart and you can use<br>
bootchart if you need more details.<br>
<div><div></div><div class="h5"><br>
Rahul<br></div></div></blockquote></div><br>This bug, which was created with your help :)<br><br><a href="https://bugzilla.redhat.com/show_bug.cgi?id=694647">https://bugzilla.redhat.com/show_bug.cgi?id=694647</a><br clear="all">
<br>