Re: [systemd-devel] Understanding systemd-analyze's plots
On Sun, Nov 27, 2011 at 1:42 PM, Gustavo Sverzut Barbieri barbi...@profusion.mobi wrote: I'd check a fresh install to avoid problem with legacy udev rules... The system was reinstalled when I went to openSUSE 12.1 RC 1 (or Beta 2, don't exactly remember). Since then, I've only updated. Greetings Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Understanding systemd-analyze's plots
On Sun, Nov 27, 2011 at 3:28 PM, Kay Sievers kay.siev...@vrfy.org wrote: There is not that much of the crazy stuff left. And if the filesystem is not on LVM or BIOS raid, most of these packages can be removed. In fact, I've masked lvm.service (=/etc/init.d/boot.lvm) because I don't have LVM and lvm.service looked like it needed a lot of time, but that did not improve the overall startup speed. Greetings Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Understanding systemd-analyze's plots
Hi, my openSUSE 12.1 system boots in about 30 seconds, and I wanted to cut that time down a bit, so I took a look at systemd-analyze's blame and plot output. But I do not really know how to interpret the results which I see in the plot [1]. The startup sequence takes 20.5 seconds in userspace, of which only the last 3 seconds seem to be spent on what I consider the interesting stuff: starting all sorts of services and finally bringing up KDM. The rest of the time seems to be spent activating the hardware, various mounts and udev. (According to the LED on my notebook's case, the disk is busy all the time.) To put my confusion into questions: 1. Why does the system need 6 seconds (from t=6.3s to t=12.3s on the plot) to activate some tmpfs mounts? 2. Why is localnet.service activating for a whole 7 seconds? I looked into it, it's only a SysV init script that sets hostname and domainname from the config in /etc, yet it's number 1 in systemd-analyze blame. 3. Why does it look like about nothing happens between t=13s and t=22s? It might be that openSUSE's unit files (or SysV leftovers) are not yet optimized for the early boot: For example, I seem to have saved some seconds by masking lvm.service (I don't use LVM at all). But that won't explain why systemd is actually slower on this stage of boot vs. the old SysV init some distro versions ago. Can someone enlighten me? Greetings Stefan [1] http://imgur.com/3U4tg ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Using systemd in user sessions
Hi, how can I configure systemd to run as non-super-user, in a login session? The only thing that seems to be related to this is the --user switch in the systemd command, but this fails with Failed to create root cgroup hierarchy and Failed to allocate manager object when run as non-root. Greetings Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Announcing libqsystemd
Hi there, I've been hacking the last few days on a Qt-based client library that wraps systemd's DBus interface. Code is hosted on KDE's Git server at [1]. I've just requested to promote this project from the scratch area to the playground area. When that happens, the remote will change to [2]. From that point, patches can also be sent in via the ReviewBoard instance at [3]. Currently, I'm working on getting the infrastructure into place. I'm approaching it like a bindings project, and try to generate most of the involved boiler-plate code automatically, so please don't wonder that most of the code is Python scripts running over incomplete C++ sources and JSON-encoded data files. The library itself uses only QtCore and QtDBus, but there are a few examples available for clients using the library which also use KDE frameworks (most prominently a proof-of-concept Plasma dataengine). The purpose of this mail is mainly to announce that an effort is going on in this direction. Unfortunately, I won't be able to reply to mails or push my commits starting from today evening (CEST) through next Saturday because of lack of connectivity. Greetings Stefan Majewsky P.S. Lennart, just in case you have trouble remembering my name: I was the one who talked to you about systemd integration in KDE at the island party on Tuesday. I would have liked to come to the BoF on Wednesday, but had an important appointment. [1] git://anongit.kde.org/scratch/majewsky/libqsystemd [2] git://anongit.kde.org/libqsystemd [3] http://reviewboard.kde.org ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
