On 7/21/2010 12:48 PM, Heath Jones wrote:
> I think you should actually give the renaming of the binary a go. If you
> rename flowd (or name of process using memory), it wont be found and
> loaded on next boot. Obviously this is a hack and not what you want to
> be relying on in a production network, but if it solves the issue then
> good. That and hassle Juniper about a longer term solution.
>
> The other solution is to remove the statement that causes the daemon to
> load on boot, but I cant remember where that is and what loads it (init
> / rc?).
>
> Killing the process first will let you check if there are any other side
> effects.
The process is required for forwarding. It can be disabled in the config, but
then all
routing stops.
--
------------------------------------------------------------------------
Christopher E. Brown <chris.br...@acsalaska.net> desk (907) 550-8393
cell (907) 632-8492
IP Engineer - ACS
------------------------------------------------------------------------
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
