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 started since boot, ordered by the time they took to
start up. If
Hi -
I am trying to figure out why systemd is getting hung up trying to
start one of my filesystems.
(Details at https://bugzilla.redhat.com/show_bug.cgi?id=692248 for
the masochists out there.)
I've reached the point where I'm booting into "emergency" mode,
opening a shell on another VT, cont
Hi,
2010/12/24 Lennart Poettering
>
> Heya,
>
> just wanted to let everybody know that I reverted the logic in
> pam_sytemd which automatically creates a cgroup in the 'cpu' hierarchy
> for every user/session, since it makes it impossible to use RT
> scheduling from user/session processes then. F
On Wed, 30.03.11 12:49, Lennart Poettering (lenn...@poettering.net) wrote:
> - There's now /run, which will act as new place for /var/run, but is
> available during early boot. There's going to be a longer announcement
> about this on fedora-devel soon.
Here it is:
http://lists.fedoraproject
Heya,
http://www.freedesktop.org/software/systemd/systemd-21.tar.bz2
Bigger changes:
- There's now a new "systemd-nspawn" tool, which is like chroot(1), but
on steroids. I'll blog about this in more detail later on.
- If the first key you type into a cryptodisk password prompt is
Backspace,
