On Saturday, February 4, 2023 11:40:41 AM EST Mark @ GMail wrote: > Both syslog and rsyslog are running, but both of them are triggered by > syslog.socket which is not running, and fails to start either on boot > or manually. > > It complains > > syslog.socket: Socket service rsyslog.service already active, refusing. I don't run any syslog daemon -- I just use the system journal. But I suspect that if rsyslog is active (running), then there is no way to obtain the socket that it is using. I do not know why you want to do such a thing, if the daemon is already running. -- Garry T. Williams _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-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/kde@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
