Re: ssh infested by systemd.resolved

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 26, 2022 at 6:06 PM Jonathan Billings <billings@xxxxxxxxxx> wrote:
>> 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

[1] https://github.com/systemd/systemd/issues/17758
[2] https://access.redhat.com/solutions/6369201
[3] https://github.com/systemd/systemd/issues/6512
[4] https://linux.debian.bugs.dist.narkive.com/2ReHgNIk/bug-780675-systemd-segfault-in-systemd-when-running-systemctl-daemon-reload

 

--
Jonathan Billings
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux