Date: Mon, 13 Apr 2015 11:52:27 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: arch@freebsd.org Subject: Re: default file descriptor limit ? Message-ID: <20150413085227.GO1394@zxy.spb.ru> In-Reply-To: <97929.1428914379@critter.freebsd.dk> References: <78759.1428912996@critter.freebsd.dk> <79209.1428913320@critter.freebsd.dk> <20150413083159.GN1394@zxy.spb.ru> <97929.1428914379@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 13, 2015 at 08:39:39AM +0000, Poul-Henning Kamp wrote: > -------- > In message <20150413083159.GN1394@zxy.spb.ru>, Slawa Olhovchenkov writes: > > >> >This wastes tons of pointless close system calls in programs which > >> >use the suboptimal but best practice: > >> > > >> > for (i = 3; i < sysconf(_SC_OPEN_MAX); i++) > >> > close(i); > >> > > >> >For reference Linux seems to default to 1024, leaving it up to > >> >massive server processes to increase the limit for themselves. > > > >This is typical only on startup, I think? > > No. This is mandatory whenever you spawn an sub process with less privilege. Hmm. 1. Whats [linux] application do this? 2. For case of reduce this limit -- how spawned application can increase this limit, if need? I am not sure, this is posible? > >May be now time to introduce new login class, for desktop users, [...] > > How about "now is the time to realize that very few processes need more > than a few tens of filedescriptors" ? > > If Linux can manage with a hardcoded default of 1024, so can we... And have many FAQs "how to overcome this restriction". Including "libc recompile"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150413085227.GO1394>