Hi Olaf, On 21.02.2014 12:05, Olaf Radicke wrote: > 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 >
Thanks for the link. I should have checked the archives before posting on the mailing list ;). As far as I can see it was not discussed how to _use_ certain features systemd provides though (such as the mentioned socket activation). But I do believe it would be interesting to be able to start a tntnet server on demand, especially because we're always looking to improve the startup time on our embedded devices. I do not have a strong opinion on whether to ship start scripts with tntnet itself. As there's a great number of different distributions, platforms and init systems out there, this task really could / should be done by the distributors. It may not even be neccessary to include the mentioned header and C files coming from systemd - but then there could be an interface that allows passing a file descriptor to the Tntnet class, not only an integer containing the port number. I just was not sure whether there are any plans regarding this topic, so I decided to ask the mailing list. :) Kind Regards, Bernhard ------------------------------------------------------------------------------ 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
