KhajitFurTrader wrote: »Setting the file handle limit manually isn't necessary anymore. The client does it by itself now.
It's very much likely that's an effect of the switch to OpenGL 4.1. It's much faster, better utilizing the hardware (e.g., whereas the ground needed two passes to be drawn in the old client using OpenGL 2.1, it now is done with only one pass).On a side note, I've noticed that my computer runs hotter since 2.3.8. I use smcFanControl from eidac.de to crank my fan and keep my computer cooler and it shows the current temp on the menu bar. I've been running 5 to 10 degrees F hotter since 2.3.8.
From the ulimit bash man page:I know the client sets the soft and hard limits both to 5000 now, I wonder if that's the culprit. Does ulimit -n 5000 only affect the soft limit, leaving the hard limit to go higher? I really don't understand why it works, but it does make the pink textures go away.
So let's open a shell and we see...The soft limit is the value that the kernel enforces for the corresponding resource. The hard limit acts as a ceiling for the soft limit.
An unprivileged process may only set its soft limit to a value in the range from 0 up to the hard limit, and (irreversibly) lower its hard limit. A privileged process can make arbitrary changes to either limit value.
If limit is given, it is the new value of the specified resource. Otherwise, the current value of the soft limit for the specified resource is printed, unless the `-H' option is supplied.
When setting new limits, if neither `-H' nor `-S' is supplied, both the hard and soft limits are set.