AW: bzr selftest (on solaris 10): too may open files
John Arbash Meinel
john at arbash-meinel.com
Mon Nov 17 19:22:01 GMT 2008
-----BEGIN PGP SIGNED MESSAGE-----
Voelker, Bernhard wrote:
>> I had this problem with another program using java recently.
>> We got around it by increasing the amount of available memory.
>> If you are root you can also try to increase the limit and see if that
> well, I'm running bzr on smaller machines:
> 4 dual-core dual-thread SPARC64-VI 2150MHz cpus, system freq: 1012MHz
> total memory = 16384MB (16GB)
> And I can't raise the limit: even if ulimit shows a greater value the
> kernel does not let me open more files - I have to talk to my admins
> if the Solaris zone the host is running in can make a difference,
> but I don't think so because it's the same in the 'global' zone.
I'm a bit curious why you would be running into problems. I don't see
any reason why bzr would need more than 256 file handles open
*concurrently*. It makes me wonder if Sun isn't re-using previously
opened file handles.
I suppose it could be a lot of things. Like it doesn't re-use a handle
that was open for writing. Or it has problems if you rename a file. Or
if you delete an open file, etc. We try not to do things to open files,
because that doesn't work on Windows, but I know if you cancel some
tests they don't always clean up perfectly.
So in the end, I would guess at something more like the python garbage
collector not releasing files properly, or some odd interaction with the
os. I certainly don't see any reason why we would have more than a
handful of file handles open concurrently.
Hmm... maybe it is the "leaking threads" from the Remote tests? I
suppose each one could be a handle or two... just a thought.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the bazaar