<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'>Hi, Lennart Thanks for your reply! > This is ancient. Please report only issues with very recent releases > of systemd upstream, thanks! Our system with this version is very stable, I'm afraid it would cause some problems if we release rootfs with the newest systemd. However, I will test with the newest one. > Most likely logind is just blocking on dbus-daemon to start up fully, > and that's the actualy culprit for you. From this boot chart, dbus.service starts after systemd-logind.service, but dbus.service takes littile time for launching. I wonder if dbus-daemon doesn't get ready for process messages even though dbus.service enter started state... <div>> Date: Fri, 3 Jul 2015 09:28:35 +0200 > From: lennart@poettering.net > To: k870818319@outlook.com > CC: systemd-devel@lists.freedesktop.org > Subject: Re: [systemd-devel] 3.7s for systemd-logind.service starting > > On Fri, 03.07.15 05:05, RayBloodworth (k870818319@outlook.com) wrote: > > > Hi, everyone > > > > I'm optimizing booting performance of my system. > > > > systemd version: 208 > > This is ancient. Please report only issues with very recent releases > of systemd upstream, thanks! > > > platform: freescale i.MX6D Cortex-A9 > > > > I found "systemd-logind.service" takes about 3.7s for starting. > > Then I added many logs about system time and found that method "manager_connect_bus()" in logind.c takes 2.4718s. > > > > Method "dbus_bus_get_private()" in "manager_connect_bus()" blocks 2.3s ... > > > > Could anyone help me with this issue? > > Most likely logind is just blocking on dbus-daemon to start up fully, > and that's the actualy culprit for you. > > Lennart > > -- > Lennart Poettering, Red Hat </div> </div></body> </html>