Make systemd-analyze dot output only lines with units matching given
glob(7) patterns. Add --from-pattern and --to-pattern options.
Without any patterns all relationships are printed as before.
A relationship must match the follwing expression:
(isempty(from-pattern) || from-pattern)
Make systemd-analyze dot output only lines with units matching given
glob(7) patterns. Add --from-pattern and --to-pattern options.
Without any patterns all relationships are printed as before.
A relationship must match the follwing expression:
(isempty(from-pattern) || from-pattern)
Lennart Poettering wrote:
Generally on Linux only the X session in the fg will get the
keypresses. If you switch away with from it, the new one in the bg will
get it instead. logind will get active hence only if there's nobody on
that specific VT who wants to take the events.
The
'Twas brillig, and Lennart Poettering at 29/03/13 15:32 did gyre and gimble:
On Fri, 29.03.13 13:29, Andrey Borzenkov (arvidj...@gmail.com) wrote:
serial-getty@.service is used only as template, and it looks like
getty-generator always links to (/usr)/lib/systemd:
from =
Same issue with make check as reported before:
http://lists.freedesktop.org/archives/systemd-devel/2013-March/009971.html
Am 29.03.2013 04:14, schrieb Lennart Poettering:
Heya,
System Five Hundred has now reached Version Two Hundred, how awesome is
that?
Mostly bug fixes.
Hi,
I'm trying to preserve my chroot-ed, systemctl-launched BIND9's logs.
To do that, I'm using a bind mount.
My problem is, it all works from command line, but not from when doing
the same thing via systemd unit file.
My question is: Why doesn't it work? What am I doing wrong here?
Before
Found it. In:
man systemd.exec
Says setting PrivateTmp=true makes sharing between processes via /tmp
impossible.
So if I change:
EDIT /etc/systemd/system/named-custom.service
- PrivateTmp=true
+ PrivateTmp=false
Now the mount is created correctly when I use the unit file, and the
logs
Hello systemd people,
I was migrating my modified service files away from .install to the new
/etc/systemd/system/foo.bar.d/*.conf setup. Along the way, I hit a bit
of a snag.
I have a custom target for when I use the CK kernel, as it is not able to
run systemd --user. So I have a
