[jka]

Thanks for highlighting the GitHub discussion of the issue.

I'd imagine the maintainers are extremely busy and may have a sense (or incentive?) to respond - in any way - to issues swiftly, and that closing them may in many cases be the most time-efficient way to keep their own work under control.

That said I agree that situations like this are frustrating for users, especially when they expose what appear to be genuine and reproducible issues.

[e12e]

I get that they're busy, and "lol, you're on an ancient version #wontfix" is quite all right as a first response (maybe a little less so for RedHat subscribers, considering the link between systemd and RedHat).

But not seing that the design seems fundamentally broken, that's more of an issue (message amplification to millions of messages, the fact that it's questionable if systemd even can use the information for meaningful ordering/dependency reseloution.... When it's not systemd doing the mounting..).