Hello Bernhard! > Bernhard Seßler <[email protected]> hat am 21. Februar 2014 um > 08:57 geschrieben: [...] > parallelize the boot process, using features like e.g. socket > activation, where systemd creates a socket and passes it to the application - > i.e. the application does not have to create it itself. The same feature also > allows to start services on demand, e.g. I've created a dropbear (SSH Server) > unit, that only starts the actual daemon when a connection on port 22 is > detected by systemd. > > Now I've also thought about doing that with an example web application we > wrote > (a standalone executable using the tntnet framework) when a connection on port > 80 is detected, but soon realized that it's not as easy to do with tntnet in > its > current state. > > As many major distributions will be switching to systemd in the near future > (e.g. Debian / Ubuntu) or already use systemd (e.g. Fedora), I was wondering > whether there are any plans to integrate (probably optional) systemd support > into tntnet? Integrating something like that seems easy enough, all in all > it's > just the sd-daemon.[h,c][1] files that need to be copied into the project and > using the systemd functions they provide (which are all backwards compatible > in > case someone's not using systemd). > > [1] http://0pointer.de/blog/projects/socket-activation.html
We are wrote about this topic short before. You find this thread here:: http://sourceforge.net/mailarchive/forum.php?thread_name=52C96325.1000504%40tntnet.org&forum_name=tntnet-general Kind Regards, Olaf ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
