* James Carlson <james.d.carlson at sun.com> [2008-04-30 20:08]: > There's no way to do that, so what the code really does is fork+exec. > In the pre-SMF world, that was a great solution. Post-SMF, no so > much. Those exec'd processes (no matter what they do) stay in the > same process contract and lurk. > > A subsequent request or problem that causes the daemon to fault causes > the original invoker -- who may well have gone on to bigger and better > things -- to take the hit. Any others who came along are unaffected, > as it's an on-demand service which runs as long as there's work.
Just so I understand: the inetd restarter's implementation of the service model is or isn't on-demand in this sense? - Stephen
