Is there a single program version of inetd?












6















inetd can make several programs with stdin input and stdout output work like programs with input and output from and to sockets, and monitor their listening sockets simultaneously.



Is there a simpler program than inetd which just works for a single program: make a single program with stdin input and stdout output work like a program with input and output from and to sockets?



Thanks.










share|improve this question


















  • 2





    If your Linux distribution is using systemd, then systemd can do that all for you (in other words, you don't need any extra software), simply by configuring a socket unit and a corresponding service unit to run your program.

    – filbranden
    Feb 14 at 18:17
















6















inetd can make several programs with stdin input and stdout output work like programs with input and output from and to sockets, and monitor their listening sockets simultaneously.



Is there a simpler program than inetd which just works for a single program: make a single program with stdin input and stdout output work like a program with input and output from and to sockets?



Thanks.










share|improve this question


















  • 2





    If your Linux distribution is using systemd, then systemd can do that all for you (in other words, you don't need any extra software), simply by configuring a socket unit and a corresponding service unit to run your program.

    – filbranden
    Feb 14 at 18:17














6












6








6


1






inetd can make several programs with stdin input and stdout output work like programs with input and output from and to sockets, and monitor their listening sockets simultaneously.



Is there a simpler program than inetd which just works for a single program: make a single program with stdin input and stdout output work like a program with input and output from and to sockets?



Thanks.










share|improve this question














inetd can make several programs with stdin input and stdout output work like programs with input and output from and to sockets, and monitor their listening sockets simultaneously.



Is there a simpler program than inetd which just works for a single program: make a single program with stdin input and stdout output work like a program with input and output from and to sockets?



Thanks.







services inetd






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 14 at 14:47









TimTim

27.8k78265485




27.8k78265485








  • 2





    If your Linux distribution is using systemd, then systemd can do that all for you (in other words, you don't need any extra software), simply by configuring a socket unit and a corresponding service unit to run your program.

    – filbranden
    Feb 14 at 18:17














  • 2





    If your Linux distribution is using systemd, then systemd can do that all for you (in other words, you don't need any extra software), simply by configuring a socket unit and a corresponding service unit to run your program.

    – filbranden
    Feb 14 at 18:17








2




2





If your Linux distribution is using systemd, then systemd can do that all for you (in other words, you don't need any extra software), simply by configuring a socket unit and a corresponding service unit to run your program.

– filbranden
Feb 14 at 18:17





If your Linux distribution is using systemd, then systemd can do that all for you (in other words, you don't need any extra software), simply by configuring a socket unit and a corresponding service unit to run your program.

– filbranden
Feb 14 at 18:17










3 Answers
3






active

oldest

votes


















16














Nmap’s Ncat can do this, with its -c or -e options:



nc -l -c bc


will listen on the default port (31337) and, when a connection is established, run bc with its standard input and output connected to the socket.



nc localhost 31337


will then connect to a “remote” bc and you can then enter bc expressions and see their result.



socat can do this too (thanks Hermann):



socat tcp-listen:31337,reuseaddr,fork EXEC:bc





share|improve this answer

































    8














    There are plenty of UCSPI-TCP tools.



    In the following, the server program is ./service, 0.0.0.0 or ::0 are the host IP addresses, and 7777 is the port number.



    There are also (not listed in this answer but documented in the various tool collections, q.v.) UCSPI-UNIX and UCSPI-LOCAL tools for AF_LOCAL sockets, tools for doing the same with FIFOs, UCSPI-SSL tools for TLS/TCP sockets, and tools for Netlink sockets.



    Bernstein ucspi-tcp



    In Daniel J. Bernstein's ucspi-tcp, there is tcpserver:


    tcpserver -v -P -R -H -l 0 0.0.0.0 7777 
    ./service


    There are IPv6-capable enhanced versions of Bernstein ucspi-tcp such as Erwin Hoffman's tcpserver:


    tcpserver -v -P -R -H -l 0 ::0 7777 
    ./service


    Bercot s6-networking



    Laurent Bercot's s6-networking has s6-tcpserver4:


    s6-tcpserver4 -v 0.0.0.0 7777 
    ./service
    and s6-tcpserver6:
    s6-tcpserver6 -v ::0 7777 
    ./service
    These are shims for other s6-networking tools.

    nosh UCSPI tools



    The nosh toolset has tcp-socket-listen and tcp-socket-accept:


    tcp-socket-listen --combine4and6 :: 7777 
    tcp-socket-accept --verbose --localname 0
    ./service
    It also has a tcpserver that is just a shim for the other two and that defaults several options on:
    tcpserver -v -l 0 :: 7777 
    ./service


    Pape ipsvd



    Gerrit Pape's ipsvd has tcpsvd:


    tcpsvd -v 0.0.0.0 7777 
    ./service


    Sampson onenetd



    Adam Sampson has a onenetd:


    onenetd -v :: 7777 
    ./service


    Further reading




    • Protocol:


      • Jonathan de Boyne Pollard (2016). The gen on the UNIX Client-Server Program Interface. Frequently Given Answers.

      • Daniel J. Bernstein (1996). UNIX Client-Server Program Interface. cr.yp.to.



    • toolsets:


      • Daniel J. Bernstein. ucspi-tcp. cr.yp.to.


      • s6-networking. Laurent Bercot. skarnet.org.

      • Jonathan de Boyne Pollard (2018). nosh. Softwares.

      • Jonathan de Boyne Pollard (2018). djbwares. Softwares.


      • ipsvd. Gerrit Pape. smarden.org.


      • onenetd. Adam Sampson. offog.org.



    • reference manuals:


      • Daniel J. Bernstein. The tcpserver program. ucspi-tcp.

      • Erwin Hoffmann. tcpserver. ucspi-tcp6. fehcom.de.


      • s6-tcpserver4. Laurent Bercot. s6-networking. skarnet.org.


      • s6-tcpserver6. Laurent Bercot. s6-networking. skarnet.org.


      • tcpsvd. ipsvd. Gerrit Pape. smarden.org.

      • Jonathan de Boyne Pollard (2019). tcpserver. nosh Guide. Softwares.

      • Jonathan de Boyne Pollard (2019). tcp-socket-listen. nosh Guide. Softwares.

      • Jonathan de Boyne Pollard (2019). tcp-socket-accept. nosh Guide. Softwares.

      • Jonathan de Boyne Pollard (2019). tcpserver. djbwares. Softwares.








    share|improve this answer





















    • 4





      This answer would be improved by leading in with the connection between the question (loosely, "programs talking to sockets") and the terminology used in the answer ("UCSPI"). If you explain what UCSPI is, then everything else will be clearer. Like most things djb, it's a boutique term, and not widely recognized.

      – gowenfawr
      Feb 14 at 21:31



















    1














    In addition to the programs listed by JdeBP, courier also uses a wrapper like this, called couriertcpd.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500642%2fis-there-a-single-program-version-of-inetd%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      16














      Nmap’s Ncat can do this, with its -c or -e options:



      nc -l -c bc


      will listen on the default port (31337) and, when a connection is established, run bc with its standard input and output connected to the socket.



      nc localhost 31337


      will then connect to a “remote” bc and you can then enter bc expressions and see their result.



      socat can do this too (thanks Hermann):



      socat tcp-listen:31337,reuseaddr,fork EXEC:bc





      share|improve this answer






























        16














        Nmap’s Ncat can do this, with its -c or -e options:



        nc -l -c bc


        will listen on the default port (31337) and, when a connection is established, run bc with its standard input and output connected to the socket.



        nc localhost 31337


        will then connect to a “remote” bc and you can then enter bc expressions and see their result.



        socat can do this too (thanks Hermann):



        socat tcp-listen:31337,reuseaddr,fork EXEC:bc





        share|improve this answer




























          16












          16








          16







          Nmap’s Ncat can do this, with its -c or -e options:



          nc -l -c bc


          will listen on the default port (31337) and, when a connection is established, run bc with its standard input and output connected to the socket.



          nc localhost 31337


          will then connect to a “remote” bc and you can then enter bc expressions and see their result.



          socat can do this too (thanks Hermann):



          socat tcp-listen:31337,reuseaddr,fork EXEC:bc





          share|improve this answer















          Nmap’s Ncat can do this, with its -c or -e options:



          nc -l -c bc


          will listen on the default port (31337) and, when a connection is established, run bc with its standard input and output connected to the socket.



          nc localhost 31337


          will then connect to a “remote” bc and you can then enter bc expressions and see their result.



          socat can do this too (thanks Hermann):



          socat tcp-listen:31337,reuseaddr,fork EXEC:bc






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 14 at 17:27

























          answered Feb 14 at 14:55









          Stephen KittStephen Kitt

          176k24401479




          176k24401479

























              8














              There are plenty of UCSPI-TCP tools.



              In the following, the server program is ./service, 0.0.0.0 or ::0 are the host IP addresses, and 7777 is the port number.



              There are also (not listed in this answer but documented in the various tool collections, q.v.) UCSPI-UNIX and UCSPI-LOCAL tools for AF_LOCAL sockets, tools for doing the same with FIFOs, UCSPI-SSL tools for TLS/TCP sockets, and tools for Netlink sockets.



              Bernstein ucspi-tcp



              In Daniel J. Bernstein's ucspi-tcp, there is tcpserver:


              tcpserver -v -P -R -H -l 0 0.0.0.0 7777 
              ./service


              There are IPv6-capable enhanced versions of Bernstein ucspi-tcp such as Erwin Hoffman's tcpserver:


              tcpserver -v -P -R -H -l 0 ::0 7777 
              ./service


              Bercot s6-networking



              Laurent Bercot's s6-networking has s6-tcpserver4:


              s6-tcpserver4 -v 0.0.0.0 7777 
              ./service
              and s6-tcpserver6:
              s6-tcpserver6 -v ::0 7777 
              ./service
              These are shims for other s6-networking tools.

              nosh UCSPI tools



              The nosh toolset has tcp-socket-listen and tcp-socket-accept:


              tcp-socket-listen --combine4and6 :: 7777 
              tcp-socket-accept --verbose --localname 0
              ./service
              It also has a tcpserver that is just a shim for the other two and that defaults several options on:
              tcpserver -v -l 0 :: 7777 
              ./service


              Pape ipsvd



              Gerrit Pape's ipsvd has tcpsvd:


              tcpsvd -v 0.0.0.0 7777 
              ./service


              Sampson onenetd



              Adam Sampson has a onenetd:


              onenetd -v :: 7777 
              ./service


              Further reading




              • Protocol:


                • Jonathan de Boyne Pollard (2016). The gen on the UNIX Client-Server Program Interface. Frequently Given Answers.

                • Daniel J. Bernstein (1996). UNIX Client-Server Program Interface. cr.yp.to.



              • toolsets:


                • Daniel J. Bernstein. ucspi-tcp. cr.yp.to.


                • s6-networking. Laurent Bercot. skarnet.org.

                • Jonathan de Boyne Pollard (2018). nosh. Softwares.

                • Jonathan de Boyne Pollard (2018). djbwares. Softwares.


                • ipsvd. Gerrit Pape. smarden.org.


                • onenetd. Adam Sampson. offog.org.



              • reference manuals:


                • Daniel J. Bernstein. The tcpserver program. ucspi-tcp.

                • Erwin Hoffmann. tcpserver. ucspi-tcp6. fehcom.de.


                • s6-tcpserver4. Laurent Bercot. s6-networking. skarnet.org.


                • s6-tcpserver6. Laurent Bercot. s6-networking. skarnet.org.


                • tcpsvd. ipsvd. Gerrit Pape. smarden.org.

                • Jonathan de Boyne Pollard (2019). tcpserver. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-listen. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-accept. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcpserver. djbwares. Softwares.








              share|improve this answer





















              • 4





                This answer would be improved by leading in with the connection between the question (loosely, "programs talking to sockets") and the terminology used in the answer ("UCSPI"). If you explain what UCSPI is, then everything else will be clearer. Like most things djb, it's a boutique term, and not widely recognized.

                – gowenfawr
                Feb 14 at 21:31
















              8














              There are plenty of UCSPI-TCP tools.



              In the following, the server program is ./service, 0.0.0.0 or ::0 are the host IP addresses, and 7777 is the port number.



              There are also (not listed in this answer but documented in the various tool collections, q.v.) UCSPI-UNIX and UCSPI-LOCAL tools for AF_LOCAL sockets, tools for doing the same with FIFOs, UCSPI-SSL tools for TLS/TCP sockets, and tools for Netlink sockets.



              Bernstein ucspi-tcp



              In Daniel J. Bernstein's ucspi-tcp, there is tcpserver:


              tcpserver -v -P -R -H -l 0 0.0.0.0 7777 
              ./service


              There are IPv6-capable enhanced versions of Bernstein ucspi-tcp such as Erwin Hoffman's tcpserver:


              tcpserver -v -P -R -H -l 0 ::0 7777 
              ./service


              Bercot s6-networking



              Laurent Bercot's s6-networking has s6-tcpserver4:


              s6-tcpserver4 -v 0.0.0.0 7777 
              ./service
              and s6-tcpserver6:
              s6-tcpserver6 -v ::0 7777 
              ./service
              These are shims for other s6-networking tools.

              nosh UCSPI tools



              The nosh toolset has tcp-socket-listen and tcp-socket-accept:


              tcp-socket-listen --combine4and6 :: 7777 
              tcp-socket-accept --verbose --localname 0
              ./service
              It also has a tcpserver that is just a shim for the other two and that defaults several options on:
              tcpserver -v -l 0 :: 7777 
              ./service


              Pape ipsvd



              Gerrit Pape's ipsvd has tcpsvd:


              tcpsvd -v 0.0.0.0 7777 
              ./service


              Sampson onenetd



              Adam Sampson has a onenetd:


              onenetd -v :: 7777 
              ./service


              Further reading




              • Protocol:


                • Jonathan de Boyne Pollard (2016). The gen on the UNIX Client-Server Program Interface. Frequently Given Answers.

                • Daniel J. Bernstein (1996). UNIX Client-Server Program Interface. cr.yp.to.



              • toolsets:


                • Daniel J. Bernstein. ucspi-tcp. cr.yp.to.


                • s6-networking. Laurent Bercot. skarnet.org.

                • Jonathan de Boyne Pollard (2018). nosh. Softwares.

                • Jonathan de Boyne Pollard (2018). djbwares. Softwares.


                • ipsvd. Gerrit Pape. smarden.org.


                • onenetd. Adam Sampson. offog.org.



              • reference manuals:


                • Daniel J. Bernstein. The tcpserver program. ucspi-tcp.

                • Erwin Hoffmann. tcpserver. ucspi-tcp6. fehcom.de.


                • s6-tcpserver4. Laurent Bercot. s6-networking. skarnet.org.


                • s6-tcpserver6. Laurent Bercot. s6-networking. skarnet.org.


                • tcpsvd. ipsvd. Gerrit Pape. smarden.org.

                • Jonathan de Boyne Pollard (2019). tcpserver. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-listen. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-accept. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcpserver. djbwares. Softwares.








              share|improve this answer





















              • 4





                This answer would be improved by leading in with the connection between the question (loosely, "programs talking to sockets") and the terminology used in the answer ("UCSPI"). If you explain what UCSPI is, then everything else will be clearer. Like most things djb, it's a boutique term, and not widely recognized.

                – gowenfawr
                Feb 14 at 21:31














              8












              8








              8







              There are plenty of UCSPI-TCP tools.



              In the following, the server program is ./service, 0.0.0.0 or ::0 are the host IP addresses, and 7777 is the port number.



              There are also (not listed in this answer but documented in the various tool collections, q.v.) UCSPI-UNIX and UCSPI-LOCAL tools for AF_LOCAL sockets, tools for doing the same with FIFOs, UCSPI-SSL tools for TLS/TCP sockets, and tools for Netlink sockets.



              Bernstein ucspi-tcp



              In Daniel J. Bernstein's ucspi-tcp, there is tcpserver:


              tcpserver -v -P -R -H -l 0 0.0.0.0 7777 
              ./service


              There are IPv6-capable enhanced versions of Bernstein ucspi-tcp such as Erwin Hoffman's tcpserver:


              tcpserver -v -P -R -H -l 0 ::0 7777 
              ./service


              Bercot s6-networking



              Laurent Bercot's s6-networking has s6-tcpserver4:


              s6-tcpserver4 -v 0.0.0.0 7777 
              ./service
              and s6-tcpserver6:
              s6-tcpserver6 -v ::0 7777 
              ./service
              These are shims for other s6-networking tools.

              nosh UCSPI tools



              The nosh toolset has tcp-socket-listen and tcp-socket-accept:


              tcp-socket-listen --combine4and6 :: 7777 
              tcp-socket-accept --verbose --localname 0
              ./service
              It also has a tcpserver that is just a shim for the other two and that defaults several options on:
              tcpserver -v -l 0 :: 7777 
              ./service


              Pape ipsvd



              Gerrit Pape's ipsvd has tcpsvd:


              tcpsvd -v 0.0.0.0 7777 
              ./service


              Sampson onenetd



              Adam Sampson has a onenetd:


              onenetd -v :: 7777 
              ./service


              Further reading




              • Protocol:


                • Jonathan de Boyne Pollard (2016). The gen on the UNIX Client-Server Program Interface. Frequently Given Answers.

                • Daniel J. Bernstein (1996). UNIX Client-Server Program Interface. cr.yp.to.



              • toolsets:


                • Daniel J. Bernstein. ucspi-tcp. cr.yp.to.


                • s6-networking. Laurent Bercot. skarnet.org.

                • Jonathan de Boyne Pollard (2018). nosh. Softwares.

                • Jonathan de Boyne Pollard (2018). djbwares. Softwares.


                • ipsvd. Gerrit Pape. smarden.org.


                • onenetd. Adam Sampson. offog.org.



              • reference manuals:


                • Daniel J. Bernstein. The tcpserver program. ucspi-tcp.

                • Erwin Hoffmann. tcpserver. ucspi-tcp6. fehcom.de.


                • s6-tcpserver4. Laurent Bercot. s6-networking. skarnet.org.


                • s6-tcpserver6. Laurent Bercot. s6-networking. skarnet.org.


                • tcpsvd. ipsvd. Gerrit Pape. smarden.org.

                • Jonathan de Boyne Pollard (2019). tcpserver. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-listen. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-accept. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcpserver. djbwares. Softwares.








              share|improve this answer















              There are plenty of UCSPI-TCP tools.



              In the following, the server program is ./service, 0.0.0.0 or ::0 are the host IP addresses, and 7777 is the port number.



              There are also (not listed in this answer but documented in the various tool collections, q.v.) UCSPI-UNIX and UCSPI-LOCAL tools for AF_LOCAL sockets, tools for doing the same with FIFOs, UCSPI-SSL tools for TLS/TCP sockets, and tools for Netlink sockets.



              Bernstein ucspi-tcp



              In Daniel J. Bernstein's ucspi-tcp, there is tcpserver:


              tcpserver -v -P -R -H -l 0 0.0.0.0 7777 
              ./service


              There are IPv6-capable enhanced versions of Bernstein ucspi-tcp such as Erwin Hoffman's tcpserver:


              tcpserver -v -P -R -H -l 0 ::0 7777 
              ./service


              Bercot s6-networking



              Laurent Bercot's s6-networking has s6-tcpserver4:


              s6-tcpserver4 -v 0.0.0.0 7777 
              ./service
              and s6-tcpserver6:
              s6-tcpserver6 -v ::0 7777 
              ./service
              These are shims for other s6-networking tools.

              nosh UCSPI tools



              The nosh toolset has tcp-socket-listen and tcp-socket-accept:


              tcp-socket-listen --combine4and6 :: 7777 
              tcp-socket-accept --verbose --localname 0
              ./service
              It also has a tcpserver that is just a shim for the other two and that defaults several options on:
              tcpserver -v -l 0 :: 7777 
              ./service


              Pape ipsvd



              Gerrit Pape's ipsvd has tcpsvd:


              tcpsvd -v 0.0.0.0 7777 
              ./service


              Sampson onenetd



              Adam Sampson has a onenetd:


              onenetd -v :: 7777 
              ./service


              Further reading




              • Protocol:


                • Jonathan de Boyne Pollard (2016). The gen on the UNIX Client-Server Program Interface. Frequently Given Answers.

                • Daniel J. Bernstein (1996). UNIX Client-Server Program Interface. cr.yp.to.



              • toolsets:


                • Daniel J. Bernstein. ucspi-tcp. cr.yp.to.


                • s6-networking. Laurent Bercot. skarnet.org.

                • Jonathan de Boyne Pollard (2018). nosh. Softwares.

                • Jonathan de Boyne Pollard (2018). djbwares. Softwares.


                • ipsvd. Gerrit Pape. smarden.org.


                • onenetd. Adam Sampson. offog.org.



              • reference manuals:


                • Daniel J. Bernstein. The tcpserver program. ucspi-tcp.

                • Erwin Hoffmann. tcpserver. ucspi-tcp6. fehcom.de.


                • s6-tcpserver4. Laurent Bercot. s6-networking. skarnet.org.


                • s6-tcpserver6. Laurent Bercot. s6-networking. skarnet.org.


                • tcpsvd. ipsvd. Gerrit Pape. smarden.org.

                • Jonathan de Boyne Pollard (2019). tcpserver. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-listen. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcp-socket-accept. nosh Guide. Softwares.

                • Jonathan de Boyne Pollard (2019). tcpserver. djbwares. Softwares.









              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Feb 15 at 14:12

























              answered Feb 14 at 15:21









              JdeBPJdeBP

              37k475176




              37k475176








              • 4





                This answer would be improved by leading in with the connection between the question (loosely, "programs talking to sockets") and the terminology used in the answer ("UCSPI"). If you explain what UCSPI is, then everything else will be clearer. Like most things djb, it's a boutique term, and not widely recognized.

                – gowenfawr
                Feb 14 at 21:31














              • 4





                This answer would be improved by leading in with the connection between the question (loosely, "programs talking to sockets") and the terminology used in the answer ("UCSPI"). If you explain what UCSPI is, then everything else will be clearer. Like most things djb, it's a boutique term, and not widely recognized.

                – gowenfawr
                Feb 14 at 21:31








              4




              4





              This answer would be improved by leading in with the connection between the question (loosely, "programs talking to sockets") and the terminology used in the answer ("UCSPI"). If you explain what UCSPI is, then everything else will be clearer. Like most things djb, it's a boutique term, and not widely recognized.

              – gowenfawr
              Feb 14 at 21:31





              This answer would be improved by leading in with the connection between the question (loosely, "programs talking to sockets") and the terminology used in the answer ("UCSPI"). If you explain what UCSPI is, then everything else will be clearer. Like most things djb, it's a boutique term, and not widely recognized.

              – gowenfawr
              Feb 14 at 21:31











              1














              In addition to the programs listed by JdeBP, courier also uses a wrapper like this, called couriertcpd.






              share|improve this answer




























                1














                In addition to the programs listed by JdeBP, courier also uses a wrapper like this, called couriertcpd.






                share|improve this answer


























                  1












                  1








                  1







                  In addition to the programs listed by JdeBP, courier also uses a wrapper like this, called couriertcpd.






                  share|improve this answer













                  In addition to the programs listed by JdeBP, courier also uses a wrapper like this, called couriertcpd.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Feb 15 at 1:10









                  ÁngelÁngel

                  1,378512




                  1,378512






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500642%2fis-there-a-single-program-version-of-inetd%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Probability when a professor distributes a quiz and homework assignment to a class of n students.

                      Aardman Animations

                      Are they similar matrix