>> The systemd --user daemon does hang around though, and it is likely it is waiting on terminating some pesky user process that wasn’t terminating properly. It isn’t the blocking process, it is the daemon trying to terminate it.
>
> Nope, absolutely everything from that ssh session was always gone, it
> was the user daemon itself that caused the hang.
[snip] Could systemd do a better job saying what it was waiting on? Yes. Is it so horribly broken it doesn’t know how to exit? No.
This kind of blanket dismissal of user feedback and refusal to believe *even the possibility* that systemd could be broken in obvious ways contributes to the sense from the community that negative feedback about systemd has been and will be ignored.
Had the response been "What kind of system was it? What test cases did you do? Which time frames?" then at least it would come across as a constructive attempt to solve the problem. But a blanket dismissal of the possibility that systemd could fail to exit cleanly as opposed to admitting that maybe they were bit by any of the previous bugs where systemd would crash on exit [1, 2, 3, 4] reinforces the sense of "systemd advocates don't listen to user feedback".
-justin
--
Jonathan Billings
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure