This manpage presents the special targets in alphabetical order, but
time-sync.target appeared in the wrong place.
---
man/systemd.special.xml.in | 28 ++--
1 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/man/systemd.special.xml.in b/man/systemd.special.x
---
Using .X[0-9]*-lock seems safe to me, but if you prefer I can write
separate lines for [0-9], [0-9][0-9], and [0-9][0-9][0-9]. Now if only
tmpfiles.d could do regexes or extglob rather than just shell-style
globs. :)
tmpfiles.d/x11.conf |2 +-
1 files changed, 1 insertions(+), 1 deletio
Many people prefer to avoid clearing /tmp and /var/tmp, and
distributions often have explicit settings for how often to clear them
if at all. Overriding those with systemd currently requires overriding
all of /usr/lib/tmpfiles.d/systemd.conf via
/etc/tmpfiles.d/systemd.conf, copying across all the
Hi!
On 08/02/2011 01:48 AM, Lennart Poettering wrote:
> Hmm, I have not seen a similar problem. My guess is though that there's
> some borkage with the RAID udev rules (are there any?): i.e. race
> between systemd spawning fsck on the md devices and some other code
> (that might be spawned from th
