-
"dbus_connection_open_private() itself is still synchronous", I did
find some dbus_connection_open_private() failures in my debugging
before(though at a very low occurrence rate). -- that's why I chose
the thread way.
Also, the shutdown_connection() may block
Hi,
2011/12/17 Michal Schmidt :
> Chen Jie wrote:
>> Let me explain it further.
>> First syslogv() in dbus may block, while rsyslog.service is starting
>> and meanwhile the kernel socket buffer was full.
>> Attachment syslog-test.c was a program simulates th
2011/12/2 Chen Jie :
> Hey,
> After did many experiments, I found it was one iteration of
> manager_loop spent ~25s:
> * dbus.service: service_enter_start_post()
> -> service_enter_running()
> --> service_set_state(s, SERVICE_RUNNING)
> ---> unit_notify()
>
Hey,
2011/12/1 Chen Jie :
> Hi,
>
> Thanks for the reply.
>
> 2011/11/30 Michal Schmidt :
>> On 11/30/2011 10:49 AM, Chen Jie wrote:
>>>
>>> (see the full syslog at
>>>
>>> http://lists.freedesktop.org/archives/dbus/attachments/2025/
to shipped to logind... thanks anyway.
Regards,
-- Chen Jie
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi,
Thanks for the reply.
2011/11/30 Michal Schmidt :
> On 11/30/2011 10:49 AM, Chen Jie wrote:
>>
>> (see the full syslog at
>>
>> http://lists.freedesktop.org/archives/dbus/attachments/2025/e9c204bb/attachment-0001.obj)
>
>
> The kernel modules failing
l]
WantedBy=multi-user.target
Any idea?
BTW, the gap between systemd-kmsg-syslogd.service stopped and rsyslog
not ready will make it lost some log messages.
Regards,
--- Chen Jie
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Forgot to mention the version of my systemd is 29.
2011/10/20 Chen Jie
> """
> What may cause dev-ttyN.device timed out?
BTW, what does "dev-ttyN.device timed out" mean?
Regards,
Chen Jie
___
systemd-d
40.988281] <31>systemd[1]: getty.target changed dead -> active
[ 41.046875] <31>systemd[1]: Job getty.target/start finished, result=done
"""
What may cause dev-ttyN.device timed out?
Regards,
Chen Jie
___
syst
2011/5/20 Lennart Poettering :
> On Fri, 20.05.11 17:40, Chen Jie (ch...@lemote.com) wrote:
>
>> 2011/5/19 Chen Jie :
>> > 2011/5/18 Kay Sievers :
>> >>
>> >> Completely different! That's an Intel Core Duo 1.4 GHz laptop:
>> >> syst
2011/5/18 Kay Sievers :
>
> 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
Good utility, thanks.
2011/3/31 Lennart Poettering
> Heya,
>
> I just added "systemd-analyze" to git. It's a little Python tool which
> can help you figuring out why your boot is not as fast as it could be.
>
> If you run "systemd-analyze blame" it will print a list of all units
> that have been
2011/3/18 Kay Sievers :
> On Fri, Mar 18, 2011 at 14:40, Gustavo Sverzut Barbieri
> wrote:
>> On Fri, Mar 18, 2011 at 10:52 AM, Andrey Borzenkov wrote:
>>> On Fri, Mar 18, 2011 at 12:35 PM, fykc...@gmail.com
>>> wrote:
>
1. What can readahead affect boot-time?
Sadly observed negative
13 matches
Mail list logo
