Re: [systemd-devel] [PATCH] cgtop: raw output option (disable conversion to human-readable units)

Hi Charles, We have done something similar to this with the cpu accounting. The option is --cpu=TYPE (There is also hidden key '%' on the tty output which toggles between different display modes). If this patch will be taken I think we should be consistent. Maybe something like --io=TYPE or --memo

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

2015-05-27 2:51 GMT+02:00 Dave Reisner : > The fact of the matter is, the last 2 releases of systemd have been > brown bag releases. Neither 219 nor 220 are useable as the tarballs are > provided. v220 doesn't even build in a large number of configurations. > v218 wasn't quite as bad, but landed 18

Re: [systemd-devel] [PATCH] cgtop: raw output option (disable conversion to human-readable units)

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing

[systemd-devel] [PATCH] cgtop: raw output option (disable conversion to human-readable units)

From: Charles Duffy --- src/cgtop/cgtop.c | 28 ++-- 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/src/cgtop/cgtop.c b/src/cgtop/cgtop.c index a390cf3..0dbac7f 100644 --- a/src/cgtop/cgtop.c +++ b/src/cgtop/cgtop.c @@ -62,6 +62,7 @@ typedef struct Group {

[systemd-devel] [PATCH] cgtop raw output option

From: Charles Duffy At present, systemd-cgtop converts quantities in bytes (memory and IO bandwidth values) to human-readable form unconditionally. Given as batch mode already exists as a supported option, there clearly is intent for cgtop to be usable with data routed to locations other than (d

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On Tue, May 26, 2015 at 04:17:07PM +0200, Lennart Poettering wrote: > On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com) > wrote: > > > Or will there be a v220.1 release shortly with releasy fix-ups? > > Well, we don't do point releases in systemd. > > In systemd git we al

Re: [systemd-devel] ExecStart vs ExecStartPre

On 05/26/2015 11:12 PM, Steven Noonan wrote: > Hi there, > > I'm wondering what the functional difference is between doing: > > ExecStartPre=/bin/foo > ExecStart=/bin/bar > > and > > ExecStart=/bin/foo > ExecStart=/bin/bar > > From my read of the systemd.service man page, they appear to have t

[systemd-devel] ExecStart vs ExecStartPre

Hi there, I'm wondering what the functional difference is between doing: ExecStartPre=/bin/foo ExecStart=/bin/bar and ExecStart=/bin/foo ExecStart=/bin/bar From my read of the systemd.service man page, they appear to have the same behavior in the common use case. The only difference I can see

Re: [systemd-devel] how to call dbus ListUnits for user units?

Well, the systemd side is already there – if you have kdbus, it'll create a user bus there, and if you have traditional dbus.service + dbus.socket, systemd will also happily connect to that. On Tue, May 26, 2015, 23:46 Chris Morgan wrote: > On Tue, May 26, 2015 at 4:05 PM, Mantas Mikulėnas > wr

Re: [systemd-devel] how to call dbus ListUnits for user units?

On Tue, May 26, 2015 at 4:05 PM, Mantas Mikulėnas wrote: > On Tue, May 26, 2015 at 10:32 PM, Chris Morgan wrote: >> >> On Tue, May 26, 2015 at 3:22 PM, Mantas Mikulėnas >> wrote: >> > On Tue, May 26, 2015 at 9:33 PM, Chris Morgan >> > wrote: >> >> >> >> But I can't seem to figure out how to do

Re: [systemd-devel] how to call dbus ListUnits for user units?

On Tue, May 26, 2015 at 10:32 PM, Chris Morgan wrote: > On Tue, May 26, 2015 at 3:22 PM, Mantas Mikulėnas > wrote: > > On Tue, May 26, 2015 at 9:33 PM, Chris Morgan > wrote: > >> > >> But I can't seem to figure out how to do the same for user units. > >> There doesn't seem to be an org.freedesk

Re: [systemd-devel] 220 udev boot regression: timeout, giving up waiting for workers to finish

On Tue, May 26, 2015 at 9:04 PM, Christian Hesse wrote: > Martin Pitt on Tue, 2015/05/26 17:11: >> Hello Tom, all, >> >> with 220 I get a severe boot time regression: >> >> $ systemd-analyze >> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s >> >> which used to be >> >>

Re: [systemd-devel] 220 udev boot regression: timeout, giving up waiting for workers to finish

On Tue, May 26, 2015 at 9:04 PM, Christian Hesse wrote: > Martin Pitt on Tue, 2015/05/26 17:11: >> Hello Tom, all, >> >> with 220 I get a severe boot time regression: >> >> $ systemd-analyze >> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s >> >> which used to be >> >>

Re: [systemd-devel] inotify_add_watch() failed: Bad file descriptor

On Tue, May 26, 2015 at 10:14 AM, Christian Hesse wrote: > Hello everybody, > > with systemd v220 I see inotify errors from udevd. I get this once: > > systemd-udevd: inotify_add_watch(9, /dev/sr0, 10) failed: Bad file descriptor > > And a lot of these: > > systemd-udevd: inotify_add_watch(9, /dev

Re: [systemd-devel] nspawn: No Return key in machinectl login?

This is stty -a from outside the container: speed 38400 baud; rows 46; columns 114; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0; -parenb -par

Re: [systemd-devel] how to call dbus ListUnits for user units?

On Tue, May 26, 2015 at 3:22 PM, Mantas Mikulėnas wrote: > On Tue, May 26, 2015 at 9:33 PM, Chris Morgan wrote: >> >> But I can't seem to figure out how to do the same for user units. >> There doesn't seem to be an org.freedesktop.systemd1 interface on my >> current user's session bus and I wasn'

Re: [systemd-devel] how to call dbus ListUnits for user units?

On Tue, May 26, 2015 at 9:33 PM, Chris Morgan wrote: > But I can't seem to figure out how to do the same for user units. > There doesn't seem to be an org.freedesktop.systemd1 interface on my > current user's session bus and I wasn't able to spot anything in the > interfaces on the system bus tha

Re: [systemd-devel] 220 udev boot regression: timeout, giving up waiting for workers to finish

Martin Pitt on Tue, 2015/05/26 17:11: > Hello Tom, all, > > with 220 I get a severe boot time regression: > > $ systemd-analyze > Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s > > which used to be > > $ systemd-analyze > Startup finished in 703ms (kernel) + 890ms

[systemd-devel] how to call dbus ListUnits for user units?

Hello. I'm able to use: dbus-send --system --print-reply --reply-timeout=2000 --type=method_call \ --dest=org.freedesktop.systemd1 \ /org/freedesktop/systemd1 org.freedesktop.systemd1.Manager.ListUnits to list system units. But I can't seem to figure out how to do the same for user units. There

Re: [systemd-devel] [PATCH] treewide: fix typos

Applied. Thanks! Tom On Tue, May 26, 2015 at 7:17 PM, Torstein Husebø wrote: > --- > NEWS| 4 ++-- > man/journal-remote.conf.xml | 2 +- > src/libsystemd/sd-bus/bus-control.c | 2 +- > src/libsystemd/sd-bus/bus-creds.c | 6 +++--- > src/shared/architect

Re: [systemd-devel] pre-release warnings?

26.05.2015 21:52, Martin Pitt wrote: Lennart Poettering [2015-05-26 18:36 +0200]: That said, I think even better would be to maybe make the support for this generic in systemctl: instead of explicitly invoking chkconfig or update-rcd, maybe we can just make systemctl invoke some fixed binary /us

Re: [systemd-devel] non-merged /usr changes [was: pre-release warnings?]

2015-05-26 19:08 GMT+02:00 Lennart Poettering : > On Tue, 26.05.15 18:52, Martin Pitt (martin.p...@ubuntu.com) wrote: > >> > > http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/patches/Fix-paths-in-man-pages.patch?h=experimental-220 >> > >> > Not enthusiastic about the idea. But th

[systemd-devel] [PATCH] treewide: fix typos

--- NEWS| 4 ++-- man/journal-remote.conf.xml | 2 +- src/libsystemd/sd-bus/bus-control.c | 2 +- src/libsystemd/sd-bus/bus-creds.c | 6 +++--- src/shared/architecture.c | 2 +- src/shared/architecture.h | 2 +- src/shared/capability.h

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On Tue, 26.05.15 19:13, Reindl Harald (h.rei...@thelounge.net) wrote: > > Am 26.05.2015 um 18:22 schrieb Lennart Poettering: > >On Tue, 26.05.15 17:57, Reindl Harald (h.rei...@thelounge.net) wrote: > >> > >>Am 26.05.2015 um 17:29 schrieb Lennart Poettering: > >>>On Tue, 26.05.15 16:39, Reindl Har

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Am 26.05.2015 um 18:22 schrieb Lennart Poettering: On Tue, 26.05.15 17:57, Reindl Harald (h.rei...@thelounge.net) wrote: Am 26.05.2015 um 17:29 schrieb Lennart Poettering: On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote: which shows that a important project like systemd

Re: [systemd-devel] non-merged /usr changes [was: pre-release warnings?]

On Tue, 26.05.15 18:52, Martin Pitt (martin.p...@ubuntu.com) wrote: > > I really don't see how the xorg.conf.d drop-in should be > > fedora-specific. That's an upstream X11 thing, and we just picked a > > name for the file and that's it. > > > > Are you saying Debian patched out supported for /et

Re: [systemd-devel] Reduce unit-loading time

On Tue, 26.05.15 09:49, Filipe Brandenburger (filbran...@google.com) wrote: > Hi, > > On Sun, May 24, 2015 at 8:41 PM, cee1 wrote: > > I tried ureadahead, but got following error: > > > > """write(2, "ureadahead: Error while tracing:"..., 59ureadahead: Error > > while tracing: No such file or di

Re: [systemd-devel] non-merged /usr changes [was: pre-release warnings?]

Lennart Poettering [2015-05-26 18:36 +0200]: > /etc/locale.conf is not a fedoraism. It has not existed on Fedora > before we introduced it. It's a systemd'ism if you so will: we looked > at where the distros configured these things and came to the > conclusion that all them were weird and nothing w

Re: [systemd-devel] Reduce unit-loading time

Hi, On Sun, May 24, 2015 at 8:41 PM, cee1 wrote: > I tried ureadahead, but got following error: > > """write(2, "ureadahead: Error while tracing:"..., 59ureadahead: Error > while tracing: No such file or directory""" > > Needs an out-of-tree kernel patch? Yes, ureadahead needs an out-of-tree ker

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Lennart Poettering [2015-05-26 18:22 +0200]: > Well, I certainly have enough things to do. We have trouble keeping up > with he amount of work that we already get, and I have no intention to > make things even more complex by maintaining multiple branches for > you, if the distros already do this a

Re: [systemd-devel] non-merged /usr changes [was: pre-release warnings?]

On Tue, 26.05.15 18:06, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hey Lennart, > > Lennart Poettering [2015-05-26 17:31 +0200]: > > But note that upstream is supposed to be non-redhat centric, and is > > supposed to support non-merged /usr. If it's really about that, I#d be > > inetersted to

Re: [systemd-devel] udev now crashes in daemon mode

Thanks, finally got around to rebooting, and udev now starts properly. However, when the cleanuphook calls "udevadm control --exit", it takes quite a while (though the system later boots normally). With --debug enabled, I see: > udevd message (EXIT) received > [10-20 seconds pass] > timeout, givin

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On Tue, 26.05.15 17:57, Reindl Harald (h.rei...@thelounge.net) wrote: > > Am 26.05.2015 um 17:29 schrieb Lennart Poettering: > >On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote: > >>which shows that a important project like systemd playing on the same level > >>as the linux ke

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

2015-05-26 17:57 GMT+02:00 Reindl Harald : >> There's a stable git tree maintained by Zbigniew, Lukas and friends, >> that carries backports for the stable releases. Most vendors should >> consider following that repo I figure. >> >> I try to help the backporting business by tagging the commits I >

Re: [systemd-devel] udev now crashes in daemon mode

Hi Tom, On Sun, May 24, 2015 at 6:30 AM, Tom Gundersen wrote: > On Sun, May 24, 2015 at 11:40 AM, Mantas Mikulėnas wrote: >> So, udev v220 crashes in my initramfs with the following message: >> >>> starting version v220 >>> Assertion 'manager->pid == getpid()' failed at src/udev/udevd.c:568, >>>

[systemd-devel] non-merged /usr changes [was: pre-release warnings?]

Hey Lennart, Lennart Poettering [2015-05-26 17:31 +0200]: > But note that upstream is supposed to be non-redhat centric, and is > supposed to support non-merged /usr. If it's really about that, I#d be > inetersted to know what these patches are about, and maybe we can move > some upstream. There'

Re: [systemd-devel] [PATCH] journal, coredump: allow relative values in some configuration options

On Mon, 25.05.15 13:48, jsyna...@redhat.com (jsyna...@redhat.com) wrote: > -static off_t arg_process_size_max = PROCESS_SIZE_MAX; > -static off_t arg_external_size_max = EXTERNAL_SIZE_MAX; > -static size_t arg_journal_size_max = JOURNAL_SIZE_MAX; > -static off_t arg_keep_free = (off_t) -1; > -stat

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Am 26.05.2015 um 17:29 schrieb Lennart Poettering: On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote: which shows that a important project like systemd playing on the same level as the linux kernel *just needs* point releases, there is a reason that the kernel has point-relea

Re: [systemd-devel] 220 udev boot regression: timeout, giving up waiting for workers to finish

On Tue, May 26, 2015 at 5:11 PM, Martin Pitt wrote: > Hello Tom, all, > > with 220 I get a severe boot time regression: > > $ systemd-analyze > Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s > > which used to be > > $ systemd-analyze > Startup finished in 703ms (kerne

Re: [systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

BOn Tue, 26.05.15 16:58, Martin Pitt (martin.p...@ubuntu.com) wrote: > > 50 non-backport patches? That sounds like a lot... > > It's not that bad, most of them are trivial, like tweaking tmpfiles.d > or some extra historic udev rules. We have quite a bunch of patches to > get rid of Fedora/RedHat

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On Tue, 26.05.15 16:39, Reindl Harald (h.rei...@thelounge.net) wrote: > > Am 26.05.2015 um 16:17 schrieb Lennart Poettering: > >On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com) > >wrote: > > > >>Or will there be a v220.1 release shortly with releasy fix-ups? > > > >Well,

[systemd-devel] 220 udev boot regression: timeout, giving up waiting for workers to finish

Hello Tom, all, with 220 I get a severe boot time regression: $ systemd-analyze Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s which used to be $ systemd-analyze Startup finished in 703ms (kernel) + 890ms (userspace) = 1.593s (this is a VM) It seems udevd --daemo

Re: [systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

Lennart Poettering [2015-05-26 16:43 +0200]: > Well, I had been trying to stabilize things since 3 weeks before the > release Ah, that's roughly when I did my last "build packages from upstream trunk" test, and indeed it looked fairly well back then. > I didn't announce this on the ML though, but

Re: [systemd-devel] How to wait for specific interface/IP?

26.05.2015 19:03, Lennart Poettering wrote: On Sat, 23.05.15 11:03, Ian Pilcher (arequip...@gmail.com) wrote: Is there a simple way to make a service require that a specific network interface/IP address be active? I have a manually set up bridge and dnsmasq configuration for my VM traffic, but

Re: [systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

On Tue, 26.05.15 16:26, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hello all, > > Dimitri John Ledkov [2015-05-26 15:12 +0100]: > > Or will there be a v220.1 release shortly with releasy fix-ups? > > Can we perhaps flip that around? I did a make dist/port our > patches/build packackages/run o

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Am 26.05.2015 um 16:17 schrieb Lennart Poettering: On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Or will there be a v220.1 release shortly with releasy fix-ups? Well, we don't do point releases in systemd. and why? just "because don't do" is not enough

[systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

Hello all, Dimitri John Ledkov [2015-05-26 15:12 +0100]: > Or will there be a v220.1 release shortly with releasy fix-ups? Can we perhaps flip that around? I did a make dist/port our patches/build packackages/run our tests round on May 11, but that was before most of the recent "hiccups" landed i

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On Tue, 26.05.15 15:12, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: > Or will there be a v220.1 release shortly with releasy fix-ups? Well, we don't do point releases in systemd. In systemd git we already have now the change that makes sd-bus and sd-event public APIs, hence v221 is

Re: [systemd-devel] Vendor default masked service

On Tue, 26.05.15 11:53, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote: > Hi, > > I was wondering if we have a way to provide vendor default masked > service? Well, so far our thinking was that if the vendor wants to make a unit completely unavailable he should simply not ship it in the first

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On 26 May 2015 at 15:10, Martin Pitt wrote: > Lennart Poettering [2015-05-26 16:06 +0200]: >> I think this has been fixed now with Tom's commit >> ee3c31bf69746c5afc764c3d0337feec1bf25f0e contributed my Marc-Antoine. > > Confirmed this morning. Sorry, I should have followed up to the ML > immediat

Re: [systemd-devel] nspawn: No Return key in machinectl login?

On Sat, 23.05.15 00:09, Tobias Hunger (tobias.hun...@gmail.com) wrote: > Hello, > > I am having a problem with one of my containers set up with > systemd-nspawn. For some reason the return key will not work most of > the time (19 out of 20 attemps) after doing machinectl login into that > machine

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

Lennart Poettering [2015-05-26 16:06 +0200]: > I think this has been fixed now with Tom's commit > ee3c31bf69746c5afc764c3d0337feec1bf25f0e contributed my Marc-Antoine. Confirmed this morning. Sorry, I should have followed up to the ML immediately. Thanks Tom! Martin -- Martin Pitt

Re: [systemd-devel] 220: --disable-audit broken?

On Fri, 22.05.15 11:27, Marc-Antoine Perennou (marc-anto...@perennou.com) wrote: > Hi, > > On 22 May 2015 at 11:16, wrote: > > hello, > > > > while building 220 I get: > > > > In file included from src/journal/audit-type.c:32:0: > > src/journal/audit_type-to-name.h: In function 'audit_t

Re: [systemd-devel] 220 tarball erroneously ships keyboard-keys-from-name.gperf

On Fri, 22.05.15 17:28, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hello, > > while packaging 220, I got the audit related build failure that was > already reported [1], but also another one: I think this has been fixed now with Tom's commit ee3c31bf69746c5afc764c3d0337feec1bf25f0e contribute

Re: [systemd-devel] systemd-nspawn: cannot join existing macvlan

On Mon, 25.05.15 16:26, Kai Krakow (hurikha...@gmail.com) wrote: > Lennart Poettering schrieb: > > > On Fri, 08.05.15 20:53, Kai Krakow (hurikha...@gmail.com) wrote: > > > >> > # systemd-nspawn -b --link-journal=try-guest --network-macvlan=enp4s0 > >> > # -- > >> > bind=/usr/portage --bind-ro=/

Re: [systemd-devel] How to wait for specific interface/IP?

On Sat, 23.05.15 11:03, Ian Pilcher (arequip...@gmail.com) wrote: > Is there a simple way to make a service require that a specific network > interface/IP address be active? > > I have a manually set up bridge and dnsmasq configuration for my VM > traffic, but dnsmasq is getting started before Ne

Re: [systemd-devel] 220 regression: path_is_mount_point() for non-directories

On Mon, 25.05.15 21:06, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hello all, > > in 220, path_is_mount_point() now always fails with "-20 ENOTDIR" when > calling it on files. This is problematic as it's perfectly valid to > have bind-mounted files; in fact, systemd's machine_id_setup() itself

Re: [systemd-devel] 219/Fedora22: NFS mounts do not set SELINUX label to nfs_t: errno=-22

On Sun, 24.05.15 15:01, Anthony Alba (ascanio.al...@gmail.com) wrote: > Hi, > > On Fedora 22, systemd 219, NFS mounts no longer acquire a default label nfs_t. > > mount 192.168.1.6:/var/exports/1 1 -orootcontext=system_u:object_r:nfs_t > mount.nfs: an incorrect mount option was specified > [ 831

Re: [systemd-devel] [PATCH] core: if PR_SET_CHILD_SUBREAPER fails, log_error instead of warning

On Sun, 24.05.15 22:41, Tom Gundersen (t...@jklm.no) wrote: > On Sat, May 23, 2015 at 6:04 PM, Cristian Rodríguez > wrote: > > It was a warning when we still supported kernel < 3.4. current > > minimum version is 3.7. > > Hm, we don't actually fail out here, but we still try to continue. > Isn't

[systemd-devel] Vendor default masked service

Hi, I was wondering if we have a way to provide vendor default masked service? Vendor default masked service has advantages like: - systemctl start won't work - dbus activation won't work It is common that an embedded system doesn't use packages, rather it ships everything in monolithic image.

[systemd-devel] crda broken with systemd 220

Hello, it seems that udev from systemd 220 does passes empty environment to a process spawned by a RUN rule. execve("/usr/sbin/crda", ["/usr/sbin/crda"], [/* 0 vars */]) = 0 This breaks crda, as it expects to see COUNTRY in its environment. -- Michał Bartoszkiewicz __

Re: [systemd-devel] Debian Bug#618862: systemd: ignores keyscript in crypttab - a possible solution

On 2015-05-26 00:05, Alberto Bertogli wrote: I hit this issue after upgrading a system that used keyscript to Jessie, and it would no longer boot with systemd [1]. That led me to look into adding a password agent for my use case, and/or creating a generic one that would invoke keyscripts as a

[systemd-devel] inotify_add_watch() failed: Bad file descriptor

Hello everybody, with systemd v220 I see inotify errors from udevd. I get this once: systemd-udevd: inotify_add_watch(9, /dev/sr0, 10) failed: Bad file descriptor And a lot of these: systemd-udevd: inotify_add_watch(9, /dev/dm-[0-9]+, 10) failed: Bad file descriptor -- main(a){char*c=/*Sch