On Tue, 2006-06-06 at 17:34 +0200, Bernhard R. Link wrote: > On Tue, Jul 19, 2005 at 09:29:21AM -0400, Joe Drew wrote: > > Xlib: connection to ":0.0" refused by server > > Xlib: Maximum number of clients reached > > > > It's possible that some other program is trying to open too many > > connections, but I have no idea what that might be. Any help in > > debugging this would be appreciated! > > Programs being nice enough (and I think they must have a window, > but that might be hidden) show up with the xlsclients program. > Whatever causes this perhaps does not, but there is a small chance that > might show the culprit. (Also note that xlsclients needs a connection to > the X server to see who is connected, so it wont be able to run after > the situation occours, except perhaps when another connection is > closed before) > > Another possibility is to look the physical connections. > netstat -axp (best run as root) should list all connections to local > servers (DISPLAY=:0 and so forth) as STREAM CONNECTED, though sadly > only the side of the Xserver is named (/tmp/.X11-unix/X0), but > heuristics can at least give hints and things to look at. > (Like a connection without filename, with a inode number one smaller > than the /tmp/.X11-unix/X0 unix is normaly a connection to the X > server)
Note that any file descriptor used by the server process counts against the limit, so there might be a file descriptor leak not directly related to (the number of) clients. Font renderer modules such as type1 or freetype would be prime suspects for that. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
