Helmut Grohne <hel...@subdivi.de> writes: > By far the more severe issue is socket activation, because it removes > the need to spell out service dependencies. We cannot infer these > dependencies later on. Instead such a wrapper must implement socket > activation in order to work correctly. This is the non-trivial problem.
Interesting point. I am wondering if it is feasible to use x/inetd for the socket activation. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87a9ln7ge8....@proton.in.awa.tohoku.ac.jp
