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. On 21 July 2010 19:35, Christopher E. Brown <chris.br...@acsalaska.net>wrote: > On 7/20/10 10:54 PM, Leigh Porter wrote: > > > > I thought that as soon as you turn MPLS on the flow mode was diabled and > > you were back to good old packet mode? > > > > -- > > Leigh > > Is puts things in packet mode, but all of the memory pre-allocs to > support flow mode remain in play. > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp