#618 drop prohibition of socket activated services
Closed: Fixed None Opened 3 years ago by zbyszek.

https://fedoraproject.org/wiki/Packaging:Systemd#Socket_activation says:

Simila to inetd, using socket activation for on-demand loading will impose a startup time penalty so we currently do not use this feature in Fedora.

and

Since Fedora currently doesn't want any services to do on-demand loading, all socket activated services must autostart.

The motivation is obsolete (if it was ever true). A full Fedora container boots in ~150 ms, so the penalty for starting a single service is negligible. Starting socket activated services on demand conserves resources.

In fact, contrary to the guidelines, there's a bunch of socket activated services already, in systmed itself: systemd-localed, systemd-machined, systemd-timedated, systemd-importd. They work just fine this way.


We discussed this at this weeks meeting (http://meetbot.fedoraproject.org/fedora-meeting-1/2016-04-28/fpc.2016-04-28-16.00.txt):

  • 618 drop prohibition of socket activated services (geppetto,


    16:08:03)
  • ACTION: drop prohibition of socket activated services (+1:7, 0:0,
    -1:0) (geppetto, 16:12:38)

Also:

Orion actually wrote this up, but it was still in the writeup state.

Announcement text:

The outdated prohibition on socket activated services was removed from the Systemd packaging guidelines.
https://fedoraproject.org/wiki/Packaging:Systemd
https://fedoraproject.org/wiki/Packaging:Systemd#Socket_activation
* https://fedorahosted.org/fpc/ticket/618

Metadata Update from @tibbs:
- Issue assigned to tibbs

2 years ago

Login to comment on this ticket.

Metadata