On Sat, Aug 25, 2001 at 05:13:57PM +0300, VDA <VDA@port.imtp.ilyichevsk.odessa.ua> wrote:
> > Simple answer - no.
> > The reason it can't is in two parts:
> > 1. these daemons create their own socket rather than recieving one
> > from inetd.
this is fine, other servers do that as well and work.
> > 2. The daemons must connect to rpcbind or portmap. Usually this daemon
> > is not running at the time inetd is started.
this would be a bug in the initscripts, inetd is a rpc client so your
initscripts better make sure it is running (when neecsssary) before inetd.
> I have rpc.portmap started just before inetd in my init script.
> BTW, how portmapper
portmap often is too slow on startup. move it earlier in the ss sequence
or add a sleep 2 somewhere.
> > These daemons must run all the time or performance will be REALLY bad. Each
> > connection may request ~ 8K bytes of data.
just like othe rudp daemons they can linger, which works fine. also,
mountd does not need to be run all the time, it is very rarely used.
having said that, this is not kernel-related and shhould be taken
elsewhere. i managed to make (userspace) mountd run from inetd, but never
managed to get the nfsd working that way.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:18 EST