Comment 6 for bug 1904920

Taking a quick glance at this, socket activation wouldn't be enough since that's only used for CLI access. We'd want multipathd running on a system that's using multipath I think, even when nobody has touched the CLI. So some kind of activation based on systemd/udev might make sense instead.

It might also be worth considering making the seed a recommends so that Pi users can remove the package.