Linux-kernel mailing list archive 1997-48,: Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)

# Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)

Daniel Ryde (ryde@tripnet.se)
Thu, 4 Dec 1997 00:15:53 +0100 (CET)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: dinon: "Re: ISSUE: lp0/lp1 incompatibility"
- Previous message: Robert Mihram: "Re: 2.1.70 still can't compile mount2.7f"
- In reply to: Dr. Werner Fink: "Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)"
- Next in thread: Chris Adams: "Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)"

On Wed, 3 Dec 1997, Dr. Werner Fink wrote:

> Are you (or nc) using SO_BINDTODEVICE on sockets and/or multiple default
> routes?

No, I don't think nc uses SO_BINDTODEVICE (I grep'ed the source). No I'm
not using multiple default routes, just three route entries (loopback +
local eth + default) apart from the pppd generated ones. The pppd ones
seems not to affect the problem (they can be there or not).

/Ryde

- Next message: dinon: "Re: ISSUE: lp0/lp1 incompatibility"
- Previous message: Robert Mihram: "Re: 2.1.70 still can't compile mount2.7f"
- In reply to: Dr. Werner Fink: "Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)"
- Next in thread: Chris Adams: "Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)"