On Friday, May 25, 2012, <a href="mailto:nalin@redhat.com">nalin@redhat.com</a> via RT  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, May 25, 2012 at 03:14:10AM -0400, Nico Williams via RT wrote:<br>

&gt; The way inetd starts wait services is so ingrained into daemons that<br>
&gt; support inetd that any change to it would have to be optional and would<br>
&gt; take a long time to be adopted.  Still, if you can find an inetd daemon<br>
&gt; that can do this then we could make krb5kdc support it.<br>
<br>
The one I had in mind was systemd:<br>
<a href="http://www.freedesktop.org/software/systemd/man/systemd.socket.html" target="_blank">http://www.freedesktop.org/software/systemd/man/systemd.socket.html</a><br>
<br>
In newer releases we still start the daemons as regular services, but<br>
being able to have systemd wait to fire them up until clients first<br>
attempt to talk to them could be handy.<br>
</blockquote><div><br></div><div>Ok, yeah, systems can do what you, or so it seems from the link you posted.</div><div><br></div><div>Nico</div>-- <span></span><span class="Apple-style-span" style> </span><div></div>