于 2011年05月20日 12:10, microcai 写道:
> 于 2011年05月20日 18:39, Lennart Poettering 写道:
>> On Fri, 20.05.11 17:40, Chen Jie (ch...@lemote.com) wrote:
>>
>>> 2011/5/19 Chen Jie <ch...@lemote.com>:
>>>> 2011/5/18 Kay Sievers <kay.siev...@vrfy.org>:
>>>>>
>>>>> Completely different! That's an Intel Core Duo 1.4 GHz laptop:
>>>>>  systemd-analyze blame | grep udev
>>>>>  87ms udev-trigger.service
>>>>>  13ms udev.service
>>>> I updated systemd(to v26) and udev(to 168), still got ~1s startup time
>>>> of udev.service plus udev-trigger.service.
>>>>
>>>> May be some distribution added udev rules cause this? I'll do a
>>>> bootchart to see the detail.
>>> See the attachment.
>>
>> There are a ton of things udev seems to be calling. A lot of it doesn't
>> look right. i.e. systemctl being called from udev doesn't look
>> right. And ps? grep? hdparm?? sync??? alsa-utils looks wrong too? mount?
>>
>> The exim script looks really borked too. And the mkdir/rm sprinkled
>> around dbus/rsyslog is suspicous too.
>>
>> I think the distro you are using is a bit too hack-happy... Your
>> downstream udev maintainers really should spend some time on cleaning up
>> those udev rules. Upstream udev doesn't ship that nonsense!
>>
>> Lennart
>>
> 
> 
> 
> Thanks ALL ~~~
> 
> My system now boots faster ~~~
> 
> See my new system boot time as attachment.
> 
> cairo.SVGSurface have problem here, so I change it to PDFSurface.
> 
> 
> 

Wait a second here!

udev.service slow down again~~~


Now I've full relized that, the problem is fsck-root.service.

udev.service stay idle as soon as fsck-root.service exit.

It is fsck-root.service that took so long to do the job.

Seems fsck always did a full check on /. Does systemd have a bug when
umount / @ shutdown?


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to