> thanks for pointing that out. In fact that is a known PR (problem > report) which is tracked with number 397439 and the fix for it is > currently being included into 9.1. > > We found that out last month as soon as we got a Customer reporting > a similar problem through a case opened with the Juniper Technical > Assistance Center.
I believe that customer was me. Or rather, I received PR397068 when the case was reported, then found that I couldn't search for this PR. And concluded that the publically available PR was PR397439. > If you happen to hit an issue or discover any misbehaviour in JunOS > which hasnt been caught during our systesting prior the official release, > please let us know and we can work on getting that fixed. I believe Richard indicated that he did just that... Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
