On Thu, Apr 2, 2020 at 5:28 PM Lennart Poettering <mzxreary@xxxxxxxxxxx> wrote: > > On Do, 02.04.20 17:22, Miklos Szeredi (miklos@xxxxxxxxxx) wrote: > > > On Thu, Apr 2, 2020 at 4:36 PM Lennart Poettering <mzxreary@xxxxxxxxxxx> 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? > > systemd cares about all mount points in PID1's mount namespace. > > The fact that mount tables can grow large is why we want something > better than constantly reparsing the whole /proc/self/mountinfo. But > filtering subsets of that is something we don't really care about. I can accept that, but you haven't given a reason why that's so. What does it do with the fact that an automount point was crossed, for example? How does that affect the operation of systemd? Thanks, Miklos
