[j-nsp] ifstrace log filling up with debug output

[Tom Beecher]

I don't see this behavior in 20.X trains, so possibly something introduced
in 21.

That being said, I think that concerns about SSD's dying because of write
volume is pretty over dramatic. The volume of logs written for everything
else is certainly much higher than this.

Worth opening a case on for sure, but this isn't going to kill drives
demonstrably faster.

On Thu, Jul 18, 2024 at 7:30 AM Joerg Staedele via juniper-nsp <
juniper-nsp at puck.nether.net> wrote:

> Hi,
>
> yes, it's the same. An no one seems to care about it? I mean, it will
> write constantly data to the local storage and may cause the flash to fail
> ...
>
> Very sad ☹
>
> Regards
>  Joerg
>
> -----Original Message-----
> From: juniper-nsp <juniper-nsp-bounces at puck.nether.net> On Behalf Of
> Timur Maryin via juniper-nsp
> Sent: Thursday, April 4, 2024 4:14 PM
> To: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] ifstrace log filling up with debug output
>
> Hi Joerg,
>
> On 23-Mar-24 15:24, Joerg Staedele via juniper-nsp wrote:
> > Hi,
> >
> > No traceoptions ... and meanwhile i've tested even with no configuration
> and after a zeroize it also does the same. I guess it’s a bug. I will try
> another version (maybe some 19.x)
>
>
> And I believe it will be the same because ifstraced  daemon is enabled
> by default on SMP systems (for a while already)
>
>
> How much data do you get in your logs?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>