Edgar Fuß
2012-09-13 16:27:21 UTC
When RPC-based entries are enabled, inetd must be started after rpcbind.
Currently, this seems to happen by chance because inetd REQUIREs DAEMON,
and nfslocking is BEFORE: DAEMON and REQUIREs nfsd, which, in turn REQUIREs
rpcbind.
So, should inetd directly REQUIRE rpcbind?
Should nfslocking also explicitly REQUIRE rpcbind?
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Currently, this seems to happen by chance because inetd REQUIREs DAEMON,
and nfslocking is BEFORE: DAEMON and REQUIREs nfsd, which, in turn REQUIREs
rpcbind.
So, should inetd directly REQUIRE rpcbind?
Should nfslocking also explicitly REQUIRE rpcbind?
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de