North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Memory leak cause of Comcast DNS problems

  • From: Jason Frisvold
  • Date: Mon Apr 18 16:09:18 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AIilkqdZ8tJxFVG17hrQDB8IIz52NFS0RYf+ul69g/oWQxPntmU6V3VY57u/msIEPU3R+4eXR5ou6kbK+YOde6L6To1Cvs+myM3kW/OKFVr3HNj0IkZWW21c4UgI8H5AnSEmiJEdTWeYC3tEDR+zI28ROGrO/gqqxaJenO//C40=

On 4/18/05, Florian Weimer <fw@deneb.enyo.de> wrote:
> Maybe the leak wasn't in the DNS service, but some other software
> component which company policy required on each server (think of
> Tivoli, antivirus software, or CSA).  Who knows?  The possiblities are
> endless.

There was, at one time, a fairly serious memory leak in Cisco CNR... 
I believe I saw a post indicating that CNR was possibly in use?

-- 
Jason 'XenoPhage' Frisvold
XenoPhage0@gmail.com