[RFC] Increase default ulimit nofile

[Jon Masters]

On Thu, 2009-05-21 at 12:31 -0400, Jon Masters wrote:
> On Thu, 2009-05-21 at 17:07 +0100, Bastien Nocera wrote:
> > On Thu, 2009-05-21 at 01:49 -0400, Jon Masters wrote:
> > <snip>
> > > I like podcasts. A lot. I also like rhythmbox (mostly). I've been
> > > wondering recently why I would occasionally not be able to download
> > > podcasts in rhythmbox. It seemed to be related to when I was connected
> > > to a particular VPN and so I had dismissed it as being network DNSness
> > > weirdness. But then it started happening much more often. Tonight, I
> > > decided it was probably more than occasional network weirdness.
> > > 
> > > So I decided "I'll just fire up gdb on rhythmbox". Many debuginfo
> > > packages, cscopes, hacked up source, etc. later on, I discover the
> > > "problem" is in abstraction layer number 2 - totem-pl-parser. So I
> > > download the source to this package also, rebuild and hack it up. I
> > > eventually discovered that various GError objects were happily telling
> > > me that the maximum number of open files had been exceeded, but totem
> > > never exposes this to rhythmbox, and the latter just has no idea what
> > > the heck is causing it to fail. Some serious fail happening there.
> > 
> > Can I have my bugzilla?
> 
> Filing upstream totem bug and RH BZ at the moment.

So the upstream totem-pl-parser bug (not catching max open files
exceeded) you need is:

http://bugzilla.gnome.org/show_bug.cgi?id=583473

> > (and some proof that totem-pl-parser is leaking descriptors...).

For clarity, rhythmbox is obviously responsible for the exceeded max
open descriptors and I don't think that is directly the fault of
totem-pl-parser. The problem with totem-pl-parser is that you wind up
receiving an ambiguous mime error that has nothing to do with the actual
problem, which is that the max open fds was exceeded.

I've also filed upstream rhythmbox bug:

http://bugzilla.gnome.org/show_bug.cgi?id=583476

Maybe if I have some time on a weekend I'll try to fix the bug - it's
unfortunately increasingly difficult for a 'non-GNOME' person to keep up
with all the goings on there...perhaps you need a podcast? ;)

Jon.