• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Track leaked Filedescriptors
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Track leaked Filedescriptors


  • Subject: Re: Track leaked Filedescriptors
  • From: Mike Smith <email@hidden>
  • Date: Sat, 28 Jan 2006 12:20:19 -0800

Message: 2
Date: Fri, 27 Jan 2006 21:54:17 +0100
From: Totte Alm <email@hidden>
Subject: Re: Track leaked Filedescriptors
To: Mike Smith <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset="us-ascii"

I can cause this to happen on any machine I've tested it on, plain
freshly installed XServes, Quad G5, Dual Gs, nothing installed except
the DB server we use.
We suspected HW problems, we even got a new XServe and send the old
one for repair, but we experienced the problem on the otehr box too
(other model), and then I made it happen.
The last thing in the system log usually is:

Jan 14 15:57:19 tor DirectoryService[41]: NetInfo connection failed
for server 127.0.0.1/local

then nothing, in any logs...
Thats why I suspect out-of file descriptors, as all other possible
solutions are gone,

I still don't understand why you think that the above is caused by a file descriptor leak. There is simply no evidence whatsoever to support that assumption.


or, its a driver level bug in OSX 10.4.x (that
doenst exist in the 10.4.3 build for intel (DTK) where this runs
flawless with the UB build.

Sadly, these sorts of problems are rarely so simple.

However, all that being said, if you were to have mentioned, for example, which particular "DB server" you're using, what the workload for it is, and how the remainder of the system is configured it might be possible to reproduce the problem and determine what is actually going on. Since you're determined that it's a descriptor leak of course, you haven't done that.

You'll get best results overall from describing the problem you're having, and including the above information so that an engineer can reproduce the actual problem on a machine in front of them, and putting it all into a bug report so that Apple can actually take a look at it. Since you have a DTK system you should have an ADC account, and so getting some attention for your bug shouldn't be too hard.

As Arnie once said, "It's not a tumor!".

 = Mike

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: Track leaked Filedescriptors
  • Next by Date: Re: Track leaked Filedescriptors
  • Previous by thread: Re: Track leaked Filedescriptors
  • Next by thread: Re: Track leaked Filedescriptors
  • Index(es):
    • Date
    • Thread