I could do something about the route monitor but not the fstat | grep route... I mean, I would have to run it in a loop endlessly until the bug happens... Even with it, it's not even sure I would catch it...
Is there some way we can fstat everything so I don't miss what's happening between 2 calls to fstat? -- -----Message d'origine----- De : Gleb Smirnoff [mailto:gleb...@freebsd.org] Envoyé : 11 septembre 2012 10:24 À : Dominic Blais Cc : freebsd-net@freebsd.org Objet : Re: kernel: arpresolve: can't allocate llinfo for 65.59.233.102 On Tue, Sep 11, 2012 at 09:19:59AM -0400, Dominic Blais wrote: D> Hi! D> D> I just noticed that it is my default route that is changing for the aforementioned in the subject IP address. What the "$?% could cause that? Could MPD push that route as default? For what reason? That IP address doesn't even belong to us. Really weird... I'd suggest you to run 'route monitor' to see exact message that inserts the route into the kernel and run periodically 'fstat | grep route' to catch the application that opens routing socket. -- Totus tuus, Glebius. _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
