[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegtRi9epdxAeoVbm+7UxkZfzC6XmD4K_5dg=RKADxy_TVA@mail.gmail.com>
Date: Thu, 2 Apr 2020 17:22:49 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Lennart Poettering <mzxreary@...inter.de>
Cc: Ian Kent <raven@...maw.net>, David Howells <dhowells@...hat.com>,
Christian Brauner <christian.brauner@...ntu.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>, dray@...hat.com,
Karel Zak <kzak@...hat.com>,
Miklos Szeredi <mszeredi@...hat.com>,
Steven Whitehouse <swhiteho@...hat.com>,
Jeff Layton <jlayton@...hat.com>, andres@...razel.de,
keyrings@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, Aleksa Sarai <cyphar@...har.com>
Subject: Re: Upcoming: Notifications, FS notifications and fsinfo()
On Thu, Apr 2, 2020 at 4:36 PM Lennart Poettering <mzxreary@...inter.de> wrote:
> You appear to be thinking about the "udisks" project or so?
Probably.
The real question is: is there a sane way to filter mount
notifications so that systemd receives only those which it is
interested in, rather than the tens of thousands that for example
autofs is managing and has nothing to do with systemd?
Is there a specific mountpoint or mountpoints that systemd is waiting
for? How exactly does this work?
Thanks,
Miklos
Powered by blists - more mailing lists