Timeline for answer to Seeking xinetd alternative for forking concurrent servers in Linux by Sean McSomething
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 10:29 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Apr 23, 2014 at 13:30 | history | edited | CommunityBot |
Fixup of bad MSO links to MSE links migration
|
|
| Apr 23, 2014 at 9:16 | history | edited | CommunityBot |
Migration of MSO links to MSE links
|
|
| Sep 11, 2013 at 23:18 | comment | added | Chap | I cant really answer all your questions here. The socket-using infrastructure was already written; the service(s) would have to be launched at startup if they were to handle connections directly. As it turned out, I wrote what I needed in Perl (which itself has to be launched at startup). The passing of the opened socket descriptor, something unnecessary with xinetd's STDIO, was something I did with a command line argument provided by the launch daemon. (BTW, "compelling arguments" are sometimes "because the CTO and Operations say so") | |
| Sep 11, 2013 at 18:38 | history | answered | Sean McSomething | CC BY-SA 3.0 |