[systemd-devel] systemd-devel listed as support confuses users (was: connection failure)

[Reindl Harald]

Am 02.07.19 um 16:10 schrieb Paul Menzel:
> Dear systemd folks,
> 
>>> -- Unit dnf-makecache.service has begun starting up.
>>> Jul 02 15:24:07 reccon.irisa.fr dnf[18029]: Metadata timer caching disabled.
>>> Jul 02 15:24:07 reccon.irisa.fr systemd[1]: Started dnf makecache.
>>> -- Subject: Unit dnf-makecache.service has finished start-up
>>> -- Defined-By: systemd
>>> -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> 
> Reading the output above, I can see, why the people contact this mailing
> list.
> 
> The output has the systemd-devel list listed as support all over the
> place.

only because of distributions ship stoneage software given that this was
fixed years ago and on the other hand common sense tells my when i have
a problem like "trying to use the Docker in GNS3" the systemd-*devel* is
likely the wrong place

https://www.gns3.com/
https://www.docker.com/

how can when trying to marry two completly unrelated packages together
and the error is "docker.service: Failed with result 'exit-code'"
stating clearly that the process gave a non-zero code back lead to the
conclusion it's a systemd topic?


"systemctl status docker.service" would even show the process and the
return code and then you debug it like any other service with or without
systemd by look at logs, google for the return code....