[systemd-devel] Antw: [EXT] Service activation
Ulrich Windl
Ulrich.Windl at rz.uni-regensburg.de
Mon Feb 14 08:27:49 UTC 2022
>>> Wol <antlists at youngman.org.uk> schrieb am 13.02.2022 um 01:03 in Nachricht
<129b4e49-d22d-7efb-7fc6-a44e5faa24db at youngman.org.uk>:
> More fun getting things to work ... :-)
>
> So I've got a service, scarletdme.service, which fires up my db backend
> for running interactively. However, I also need a socket service for
> remote connections.
>
> I've got the xinetd files, but if I'm running systemd, I want to use
> systemd :-)
>
> So I've written scarletdme.socket, and scarletdme at .service, but the more
> I read, the more I don't understand ...
>
> Do I enable scarletdme.socket the same as anything else eg "systemctl
> enable scarletdme.socket"? How does it know the difference between
> scarletdme.service and scarletdme at .service? I get the impression I need
> to put something in the .socket file to make it use scarletdme@ rather
> than scarletdme?
>
>
> And once I've got all that sorted, I'm betting I'm going to have grief
> getting it to work properly, so while it's not much to do with systemd,
> is there any way I can get systemd to log all traffic back and forth so
> I can debug it?
Maybe understandable documentation is where xinetd is still better tahn systemd ;-)
>
> Cheers,
> Wol
More information about the systemd-devel
mailing list