Re: [systemd-devel] Jenkins Failing and Not Updating Github Mirror
On Wed, 28 Jan 2015 03:42:33 +0100 Lennart Poettering wrote: > On Sun, 18.01.15 01:58, Simon Peeters (peeters.si...@gmail.com) wrote: > > > 2015-01-18 1:28 GMT+01:00 Chris Atkinson : > > > It looks like Jenkins has been failing to build for the last > > > three days and hasn't updated the Github mirror for a similar > > > period (since commit 435fc3176520a58f1c20ccb983c9fb40b30a1471). > > > > > > https://github.com/systemd/systemd > > > http://systemd.getpantheon.com:8080/jenkins/ > > > > > > Regards, > > impl.cc(344)] Failed to connect to MCS endpoint with error -106 [16682:16709:0128/072106:ERROR:connection_factory_impl.cc(344)] Failed to connect to MCS endpoint with error -105 [16682:16682:0128/072753:ERROR:navigation_entry_screenshot_manager.cc(152)] Invalid entry with unique id: 788 [WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED [16682:16682:0128/072935:ERROR:navigation_entry_screenshot_manager.cc(152)] Invalid entry with unique id: 793 [3,614770944:12:47:07.051220] Native Client modul > > so a quick analysis: > > > > The build initially broke on > > 30535c16924a3da7b47ea87190d929d617d95c5a (nspawn: add file system > > locks for controlling access to container images), due to missing > > kernel #defines probably triggered by an older kernel on the > > jenkins machine. This was fixed in > > f4a53250acb3aea2eb5ebed059887b9417afbd9e (missing: add macros for > > OFD locks), but unfortunately a missing zlib dependency introduced > > by edce2aed3aa93b84f7b4c70412bdb665da2977b0 (import: support > > importing qcow2 images) had already broken the build again. > > > > So the solution would be to make zlib available on the jenkins > > machine (David?), or make zlib an optional dep (Lennart?). > > I now made it build-time optional, as it always was supposed to > be. Let's see if this fixes Jenkins again. > > Lennart > Github is updated through 3b48ce4ec4639437ca3db344962ed37b0c83ea9a and Jenkins last successfully built at Jan 28, 2015 4:06:36 PM, so it appears all is well. Thanks Lennart. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 05/11] tmpfiles: add 'a' type to set ACLs
s/aditional/additional/ Regards, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Jenkins Failing and Not Updating Github Mirror
It looks like Jenkins has been failing to build for the last three days and hasn't updated the Github mirror for a similar period (since commit 435fc3176520a58f1c20ccb983c9fb40b30a1471). https://github.com/systemd/systemd http://systemd.getpantheon.com:8080/jenkins/ Regards, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] Grammar changes to catalog
See attached patch. Regards,>From 8c77af83fe18dbb0d2230cbfc619a7e0a66f5183 Mon Sep 17 00:00:00 2001 From: Chris Atkinson Date: Tue, 13 Jan 2015 10:06:25 -0500 Subject: [PATCH] Grammar changes to catalog --- catalog/systemd.catalog | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/catalog/systemd.catalog b/catalog/systemd.catalog index 3c2fe64..4488c83 100644 --- a/catalog/systemd.catalog +++ b/catalog/systemd.catalog @@ -23,15 +23,15 @@ # For an explanation why we do all this, see https://xkcd.com/1024/ -- f77379a8490b408bbe5f6940505a777b -Subject: The Journal has been started +Subject: The journal has been started Defined-By: systemd Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -The system journal process has been starting up, opened the journal +The system journal process has started up, opened the journal files for writing and is now ready to process requests. -- d93fb3c9c24d451a97cea615ce59c00b -Subject: The Journal has been stopped +Subject: The journal has been stopped Defined-By: systemd Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel @@ -50,8 +50,8 @@ from the service have been dropped. Note that only messages from the service in question have been dropped, other services' messages are unaffected. -The limits when messages are dropped may be configured with -RateLimitInterval= and RateLimitBurst= in +The limits controlling when messages are dropped may be configured +with RateLimitInterval= and RateLimitBurst= in /etc/systemd/journald.conf. See journald.conf(5) for details. -- e9bf28e6e834481bb6f48f548ad13606 @@ -96,7 +96,7 @@ A new session with the ID @SESSION_ID@ has been created for the user @USER_ID@. The leading process of the session is @LEADER@. -- 3354939424b4456d9802ca8333ed424a -Subject: A session @SESSION_ID@ has been terminated +Subject: Session @SESSION_ID@ has been terminated Defined-By: systemd Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat @@ -112,7 +112,7 @@ Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat A new seat @SEAT_ID@ has been configured and is now available. -- e7852bfe46784ed0accde04bc864c2d5 -Subject: A seat @SEAT_ID@ has now been removed +Subject: Seat @SEAT_ID@ has now been removed Defined-By: systemd Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat @@ -178,7 +178,7 @@ Systemd shutdown has been initiated. The shutdown has now begun and all system services are terminated and all file systems unmounted. -- 7d4958e842da4a758f6c1cdc7b36dcc5 -Subject: Unit @UNIT@ has begun with start-up +Subject: Unit @UNIT@ has begun start-up Defined-By: systemd Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel @@ -217,11 +217,11 @@ Unit @UNIT@ has failed. The result is @RESULT@. -- d34d037fff1847e6ae669a370e694725 -Subject: Unit @UNIT@ has begun with reloading its configuration +Subject: Unit @UNIT@ has begun reloading its configuration Defined-By: systemd Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -Unit @UNIT@ has begun with reloading its configuration +Unit @UNIT@ has begun reloading its configuration -- 7b05ebc668384222baa8881179cfda54 Subject: Unit @UNIT@ has finished reloading its configuration @@ -239,7 +239,7 @@ Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel The process @EXECUTABLE@ could not be executed and failed. -The error number returned while executing this process is @ERRNO@. +The error number returned by this process is @ERRNO@. -- 0027229ca0644181a76c4e92458afa2e Subject: One or more messages could not be forwarded to syslog -- 2.2.1 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] Clarify path escaping and reference systemd-escape
See Bug 87688 (https://bugs.freedesktop.org/show_bug.cgi?id=87688). This patch adds more detail to the description of how path escaping operates and provides a pointer to the systemd-escape program. Either would serve to answer the question raised in the bug report, so hopefully this will allow it to be closed. Regards>From 84fd39e106a13ec8a546c7d8ecc114f2901d1d82 Mon Sep 17 00:00:00 2001 From: Chris Atkinson Date: Thu, 1 Jan 2015 16:16:56 -0500 Subject: [PATCH 2/2] Clarify path escaping and reference systemd-escape --- man/systemd.unit.xml | 17 +++-- 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 1afa600..39ea429 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -229,12 +229,17 @@ the file system namespace. If this applies, a special way to escape the path name is used, so that the result is usable as part of a filename. Basically, -given a path, "/" is replaced by "-", and all -unprintable characters and the "-" are replaced by -C-style "\x2d" escapes. The root directory "/" is -encoded as single dash, while otherwise the initial -and ending "/" is removed from all paths during -transformation. This escaping is reversible. +given a path, "/" is replaced by "-" and all other +characters which are not ASCII alphanumerics are +replaced by C-style "\x2d" escapes (except that "_" +is never replaced and "." is only replaced when it +would be the first character in the escaped path). +The root directory "/" is encoded as single dash, +while otherwise the initial and ending "/" are removed +from all paths during transformation. This escaping +is reversible. Properly escaped paths can be generated +using the systemd-escape1 +command. Optionally, units may be instantiated from a template file at runtime. This allows creation of -- 2.2.1 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] Clarify effect when both calendar day and date are listed in timer
See bug 87859 (https://bugs.freedesktop.org/show_bug.cgi?id=87859). Bug reporter found the language describing the effect of specifying both a day and date unclear; hopefully the attached patch will clarify and allow the bug to be closed. Happy New Year to all,>From c118fbac2799e7d7d441c16f5cab0747ebe58f93 Mon Sep 17 00:00:00 2001 From: Chris Atkinson Date: Wed, 31 Dec 2014 21:39:24 -0500 Subject: [PATCH] Clarify effect when both calendar day and date listed in timer --- man/systemd.time.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/systemd.time.xml b/man/systemd.time.xml index f35ccd7..2e64089 100644 --- a/man/systemd.time.xml +++ b/man/systemd.time.xml @@ -213,8 +213,8 @@ Thu,Fri 2012-*-1,5 11:12:13 The above refers to 11:12:13 of the first or -fifth day of any month of the year 2012, given that it -is a Thursday or Friday. +fifth day of any month of the year 2012, but only if that +day is a Thursday or Friday. The weekday specification is optional. If specified, it should consist of one or more English -- 2.2.1 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] blkid: Warn when rejecting a superblock with a bad csum
Should the line: PKG_CHECK_MODULES(BLKID, [ blkid >= 2.24 ], instead read PKG_CHECK_MODULES(BLKID, [ blkid >= 2.25 ], instead since the commit message appears to mandate 2.25 not 2.24? Regards, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] build issues & "enabled" output in `systemctl status`
I had the same problem and can confirm that it now builds for me (including the Python stuff). Regards, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [BUG] too many rfkill services
I had the same issue with rfkill as Łukasz did. I have rebuilt including commit 4844262f25a3ff6bd23de05a0a6f84a8e2983d74. I tested by cycling suspend/resume 15 times without reboot, and did not experience any failed phantom rfkill services. I also tested rfkill functionality, and the state of a soft-blocked rfkill switch survived a suspend/resume and a reboot. Hope this helps, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] DISTRO_PORTING: Full path for /usr/lib/systemd/systemd
The systemd binary was moved from /usr/bin/systemd to /usr/lib/systemd/systemd (commit e0d25329b23a43332ea340f9907721873a316f4e) and is thus no longer in $PATH. This adds the absolute path /usr/lib/systemd/systemd to DISTRO_PORTING and does grammar/punctuation cleanup. Regards,>From fd6831e6568d7a57989ce3410be46d870523b827 Mon Sep 17 00:00:00 2001 From: Chris Atkinson Date: Tue, 2 Dec 2014 08:30:59 -0500 Subject: [PATCH] Full path for /usr/lib/systemd/systemd; grammar/punctuation --- DISTRO_PORTING | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/DISTRO_PORTING b/DISTRO_PORTING index d799e53..5bca90f 100644 --- a/DISTRO_PORTING +++ b/DISTRO_PORTING @@ -15,17 +15,17 @@ HOWTO: --with-kbd-setfont= --with-tty-gid= -2) Try it out. Play around with 'systemd --test --system' for -a test run of systemd without booting. This will read the unit -files and print the initial transaction it would execute -during boot-up. This will also inform you about ordering loops -and suchlike. +2) Try it out. Play around (as an ordinary user) with +'/usr/lib/systemd/systemd --test --system' for a test run +of systemd without booting. This will read the unit files and +print the initial transaction it would execute during boot-up. +This will also inform you about ordering loops and suchlike. CONTRIBUTING UPSTREAM: -We do generally no longer accept distribution-specific +We generally no longer accept distribution-specific patches to systemd upstream. If you have to make changes to -systemd's source code to make it work on your distribution: +systemd's source code to make it work on your distribution, unless your code is generic enough to be generally useful, we are unlikely to merge it. Please always consider adopting the upstream defaults. If that is not possible, please maintain -- 2.1.3 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] Delete ZX as sole compression; "Compress=" as boolean
In man journald.conf, removes reference to XZ as sole form of compression. See commit d89c8fdf48c7bad5816b9f2e77e8361721f22517. In man coredump.conf, clarifies that "Compression=" controls existence, not type, of compression. Regards,>From c8e0efc6226f27171d57706eb1a864d05d7e60e2 Mon Sep 17 00:00:00 2001 From: Chris Atkinson Date: Sun, 30 Nov 2014 21:51:49 -0500 Subject: [PATCH] Delete ZX as sole compression; "Compress=" as boolean --- man/coredump.conf.xml | 2 +- man/journald.conf.xml | 5 ++--- 2 files changed, 3 insertions(+), 4 deletions(-) diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml index 5d54407..7046460 100644 --- a/man/coredump.conf.xml +++ b/man/coredump.conf.xml @@ -99,7 +99,7 @@ Compress= -Controls the type of compression for external +Controls compression for external storage. Takes a boolean argument, defaults to yes. diff --git a/man/journald.conf.xml b/man/journald.conf.xml index bf0b944..e240b7c 100644 --- a/man/journald.conf.xml +++ b/man/journald.conf.xml @@ -123,9 +123,8 @@ value. If enabled (the default), data objects that shall be stored in the journal and are larger than a certain -threshold are compressed with the XZ -compression algorithm before they are -written to the file +threshold are compressed before they +are written to the file system. -- 2.1.3 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] Documentation changes to reflect that isolate is for target and snapshot only and that no extension filenames default to .target.
On Fri, 28 Nov 2014 23:43:33 +0100
Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Nov 28, 2014 at 03:37:25PM -0500, Chris Atkinson wrote:
> > See
> >
> > http://lists.freedesktop.org/archives/systemd-devel/2014-November/025644.html
> >
> > et seq.
> Hi,
> your patch is line-wrapper. Please resend it using git send-email
> or as an attachment.
>
> Zbyszek
Sorry about that. Patch attached.
Regards,
>From a31a4cde5df338067f3dbb25f47cfdcfc9ef83cd Mon Sep 17 00:00:00 2001
From: Chris Atkinson
Date: Fri, 28 Nov 2014 15:27:56 -0500
Subject: [PATCH] Documentation changes to reflect that isolate is for target
and snapshot only and that no extension filenames default to .target.
---
man/systemctl.xml | 12
src/systemctl/systemctl.c | 2 +-
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 4a7abab..e6f438c 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -705,7 +705,10 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
Start the unit specified on the command line and its
-dependencies and stop all others.
+dependencies and stop all others. This applies only to
+target and snapshot units.
+If a filename with no extension is given, an extension of
+ .target will be assumed.
This is similar to changing the runlevel in a
traditional init system. The isolate
@@ -713,7 +716,8 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
in the new unit, possibly including the graphical
environment or terminal you are currently using.
-Note that this is allowed only on units where
+Note that for target units this is
+allowed only on units where
AllowIsolate= is enabled. See
systemd.unit5
for details.
@@ -1597,9 +1601,9 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
# systemctl start sshd and
# systemctl start sshd.service
are equivalent, as are
- # systemctl isolate snapshot-11
+ # systemctl isolate default
and
- # systemctl isolate snapshot-11.snapshot
+ # systemctl isolate default.target
Note that (absolute) paths to device nodes are automatically
converted to device unit names, and other (absolute) paths to
mount unit names.
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index ffb97df..2176f15 100644
--- a/src/systemctl/systemctl.c
+++ b/src/systemctl/systemctl.c
@@ -5770,7 +5770,7 @@ static void systemctl_help(void) {
" otherwise start or restart\n"
" reload-or-try-restart NAME... Reload one or more units if possible,\n"
" otherwise restart if active\n"
- " isolate NAMEStart one unit and stop all others\n"
+ " isolate NAMEStart one target/snapshot unit and stop all others\n"
" kill NAME...Send signal to processes of a unit\n"
" is-active PATTERN...Check whether units are active\n"
" is-failed PATTERN...Check whether units are failed\n"
--
2.1.3
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] Documentation changes to reflect that isolate is for target and snapshot only and that no extension filenames default to .target.
See
http://lists.freedesktop.org/archives/systemd-devel/2014-November/025644.html
et seq.
---
man/systemctl.xml | 12
src/systemctl/systemctl.c | 2 +-
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 4a7abab..e6f438c 100644
--- a/man/systemctl.xml
+++ b/man/systemctl.xml
@@ -705,7 +705,10 @@ kobject-uevent 1 systemd-udevd-kernel.socket
systemd-udevd.service
Start the unit specified on the command line and its
-dependencies and stop all others.
+dependencies and stop all others. This applies only to
+dependencies and stop all others. This applies only to
+ .target will be assumed.
traditional init system. The isolate
@@ -713,7 +716,8 @@
-Note that this is allowed only on units where
+Note that for target units this
is
+allowed only on units where
AllowIsolate= is enabled. See
systemd.unit5
for details.
@@ -1597,9 +1601,9 @@ kobject-uevent 1 systemd-udevd-kernel.socket
systemd-udevd.service # systemctl start
sshd and # systemctl start
sshd.service are equivalent, as are
- # systemctl isolate snapshot-11
+ # systemctl isolate default
and
- # systemctl isolate
snapshot-11.snapshot
+ # systemctl isolate
default.target Note that (absolute) paths to device
nodes are automatically converted to device unit names, and other
(absolute) paths to mount unit names.
diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c
index ffb97df..2176f15 100644
--- a/src/systemctl/systemctl.c
+++ b/src/systemctl/systemctl.c
@@ -5770,7 +5770,7 @@ static void systemctl_help(void) {
" otherwise start or
restart\n" " reload-or-try-restart NAME... Reload one or more units
if possible,\n" " otherwise restart if
active\n"
- " isolate NAMEStart one unit and
stop all others\n"
+ " isolate NAMEStart one
target/snapshot unit and stop all others\n" " kill
NAME...Send signal to processes of a unit\n" "
is-active PATTERN...Check whether units are active\n" "
is-failed PATTERN...Check whether units are failed\n"
--
2.1.3
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemctl isolate "foo.service" expands to "foo.service.target"
Commit e80733be33e52d8ab2f1ae845326d39c600f5612 seems to have done the trick. I'm able to start, stop and status services, isolate .target and .snapshot files and a filename with no extension following "isolate" is treated as a .target, all of which seems right. The systemctl man page will still need tweaking; I will do so unless you object. Regards, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemctl isolate "foo.service" expands to "foo.service.target"
The commit (5e03c6e3b517286bbd65b48d88f60e5b83721894) seems to be
having some side effects.
When I attempt to query status, stop or start a service I get
the following:
$ sudo systemctl stop transmission
Assertion 'suffix' failed at src/shared/unit-name.c:515, function
unit_name_mangle_with_suffix(). Aborting.
journalctl shows the following coredump:
Process 4687 (systemctl) of user 0 dumped core.
Stack trace of thread 4687:
#0 0x7fb3bf640a97 raise (libc.so.6)
#1 0x7fb3bf641e6a abort (libc.so.6)
#2 0x7fb3c051b462 log_assert_failed (systemctl)
#3 0x7fb3c052e4ef unit_name_mangle_with_suffix (systemctl)
#4 0x7fb3c050d12d expand_names.lto_priv.398 (systemctl)
#5 0x7fb3c05185cc check_unit_generic (systemctl)
#6 0x7fb3c050abe6 main (systemctl)
#7 0x7fb3bf62d040 __libc_start_main (libc.so.6)
#8 0x7fb3c050b64c _start (systemctl)
Attempts to isolate a snapshot fail silently with the same coredump.
Attempts to isolate to default.target worked but attempts to isolate
back to a user-defined .target failed.
systemd was compiled with glibc 2.20 and the following flags:
--libexecdir=/usr/lib \
--localstatedir=/var \
--sysconfdir=/etc \
--enable-introspection \
--enable-gtk-doc \
--enable-compat-libs \
--disable-audit \
--disable-ima \
--disable-multi-seat-x \
--disable-smack \
--with-sysvinit-path= \
--with-sysvrcnd-path= \
--with-firmware-path="/usr/lib/firmware/updates:/usr/lib/firmware"\
--with-ntp-servers="${timeservers[*]}"
Please let me know if there are any items you'd like me to test or
additional information you would find useful.
Regards,
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemctl isolate "foo.service" expands to "foo.service.target"
How does this interact with snapshots? While I was looking at man systemctl it seems that one uses isolate to restore to a previous snapshot: Snapshot Commands snapshot [NAME] Create a snapshot. If a snapshot name is specified, the new snapshot will be named after it. If none is specified, an automatic snapshot name is generated. In either case, the snapshot name used is printed to standard output, unless --quiet is specified. A snapshot refers to a saved state of the systemd manager. It is implemented itself as a unit that is generated dynamically with this command and has dependencies on all units active at the time. At a later time, the user may return to this state by using the isolate command on the snapshot unit. Snapshots are only useful for saving and restoring which units are running or are stopped, they do not save/restore any other state. Snapshots are dynamic and lost on reboot. I created a named snapshot: $ sudo systemctl snapshot derpy derpy.snapshot I tried restoring the named snapshot, but the mandatory mangling to .target got in the way: $ sudo systemctl isolate derpy.snapshot Failed to start derpy.snapshot.target: Operation refused, unit may not be isolated. Results were the same with an automatically named snapshot. Did I misunderstand the man page and there's some other way to restore a snapshot? Thanks, ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] man/logind.conf.xml: make consistent with default logind.conf
See Bug 86263 --- man/logind.conf.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man/logind.conf.xml b/man/logind.conf.xml index d245bf4..d37fcba 100644 --- a/man/logind.conf.xml +++ b/man/logind.conf.xml @@ -281,17 +281,17 @@ sleep keys and the lid switch are subject to inhibitor locks. These settings take boolean arguments. If -off, the inhibitor +no, the inhibitor locks taken by applications in order to block the requested operation are -respected. If on, +respected. If yes, the requested operation is executed in any case. PowerKeyIgnoreInhibited=, SuspendKeyIgnoreInhibited= and HibernateKeyIgnoreInhibited= -default to off. +default to no. LidSwitchIgnoreInhibited= defaults to yes. This means -- 2.1.3 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
