Thanks for Todd B. Acheson <acheson_at_ohiou.edu>, whose response is below. My original question is at the bottom.
> There is no other side effect to not starting randd other than weaker
> random numbers. You can also safely kill it if it is running.
>
> You can rename the binary so it is not found at startup or there is and
> Env. variable you can set, which I can't remember so that the
> dcestartup/decsetup don't start it ( this is in the documentation
> somewhere).
My question was:
> We have some systems with 4.0F running DCE services only for RPC support.
> Whenever we enable the DCE services, the 'randd' process -a daemon for pre-
> generation of random numbers- appears with a nice value of 2. This is a very nice
> process, then.
>
> However, other processes fail to obtain full attention of the system due to this
> daemon running.
>
> The DCE documentation seems to suggest that killing randd will not harm the
> system. The performance of DCE itself may be reduced, but that is a price I am
> willing to pay; that is, if that is the only thing to pay.
>
> Thus, my question to you is two-fold:
>
> 1. Is there anything else I should worry about if I configure the system to not
> start 'randd' on the startup sequence?
>
> 2. How can I configure the system to not start 'randd' automatically while
> keeping the DCE support for RPC?
Carlos Martinez-Mascarua
Project Engineer
ALSTOM ESCA
Received on Fri Aug 18 2000 - 21:04:20 NZST