[asterisk-bugs] [JIRA] (ASTERISK-25541) add socket activation support
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Wed Nov 11 09:36:33 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton closed ASTERISK-25541.
-----------------------------------
Resolution: Suspended
> add socket activation support
> -----------------------------
>
> Key: ASTERISK-25541
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25541
> Project: Asterisk
> Issue Type: Improvement
> Security Level: None
> Reporter: Max
>
> Having (optional) support for socket activation in Asterisk would bring several benefits:
> # Security: systemd can listen on privileged ports or socket paths and start Asterisk with privileges already dropped.
> # Major upgrades or reconfigurations of Asterisk requiring a full restart are possible without having the listening socket(s) ever go away.
> # Any service dependent on Asterisk doesn't have to wait for it to finish starting (or start at all).
> # We can be absolutely sure that we always bind to existing IP addresses on all desired network interfaces - no race conditions with network bring-up, systemd takes care of that for us.
> Here is some useful documentation:
> http://0pointer.de/blog/projects/socket-activation.html
> http://0pointer.de/blog/projects/socket-activation2.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list