docker-systemctl-replacement icon indicating copy to clipboard operation
docker-systemctl-replacement copied to clipboard

socket units not supported

Open jamie-at-sas opened this issue 7 years ago • 3 comments

One feature of systemd is to allow a systemd.socket file to be created in parallel with a .service file.

In other words, you might have

foo.service foo.socket

In the same directory.

These .socket files are apparently unsupported by systemctl.py.

Note also that they can have the same %t that is currently not supported in .service files, as reported in issue #29.

jamie-at-sas avatar Jul 13 '18 14:07 jamie-at-sas

I did never have a need to support sockets.

Patches may need to change a lot of things as only *.service files are scanned. And those have a lmited concept of starting other services before.

gdraheim avatar Jul 16 '18 20:07 gdraheim

I am going to set this to wontfix by now. May be you have an implementation idea how to actualy do it in a script like systemctl.py ?

gdraheim avatar Jul 21 '18 09:07 gdraheim

I have put the basic infrastructure into place - however Accept=no will simply start the underlying service unit. An actual port-listen, required for Accept=yes, is not attempted. But that's the original use case?

gdraheim avatar Oct 24 '19 12:10 gdraheim