| |||||||||||||
|
| |||||||||||||
The road forward for systemdThe road forward for systemdPosted May 27, 2010 7:44 UTC (Thu) by cyperpunks (subscriber, #39406)Parent article: The road forward for systemd
How will sysstemd work with e.g. ypbind?
Should a getent call trigger ypbind to start?
(Log in to post comments)
The road forward for systemd Posted May 27, 2010 8:49 UTC (Thu) by neilbrown (subscriber, #359) [Link]
I don't know if the current code does, but it certainly good.
Some versions of inetd will listen for RPC services (like ypbind or ypserv) and start the daemon only on demand.
It might be a bit tricky if portmap (or rpcbind) were started on demand. You would want to be able to feed it a list of programs/binding to be able to report immediately rather than waiting for them to be registered.
But it is certainly possible.
The road forward for systemd Posted May 31, 2010 17:06 UTC (Mon) by mezcalero (guest, #45103) [Link]
I have already patched rpcbind to be socket-activated. It is then started as soon as some client wants to query or register a service; or alternatively at startup but parallelized.
The road forward for systemd Posted May 31, 2010 17:05 UTC (Mon) by mezcalero (guest, #45103) [Link]
Yes, it should. But most likely you should also run it right-away on bootup. Since name lookups will be necessary anyway it would be only smart to start it right-away and not delay it until it is actually used.
|
|
||||||||||||