Am 21.02.2014 15:17, schrieb Julian Wiesener: > Hi, > > On Fri, 2014-02-21 at 13:01 +0100, Bernhard Seßler wrote: >> 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. > While there is no support for that, you still can build it on your own > using the standalone-model of tntnet (*1). I suspect that passing the > socket to the application instead of just letting it open it for its > self, will be the biggest issue. However, i would rather opt for an more > generic solution for that instead of systemd specific modifications. If > you have trouble passing the socket or need any modification in tntnet, > please let us know, IRC might be a better option. > > > > Regards, > Julian > Hi,
the last discussion was about writing startup scripts for systemd or other init systems. We agreed, that this makes no sense. But integrating into systemd with socket activation is a different thing. This can't be just done outside the code. We need some support in tntnet for that. The question is, how to do that. Julian is right, that it may be a option to implement a more generic solution. Currently it is not possible to pass just a file descriptor to tntnet. I feel, that it makes really sense to implement something like that. So now it is on our TODO list;-) Tommi ------------------------------------------------------------------------------ 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
