Maximum number of clients reached?

[Dan Stromberg]

I'm pretty sure it's the first message below I'm getting:

$ strings -a $(which Xvnc) | grep -i maximum
Maximum number of clients reached
Maximum permitted length of an incoming clipboard update

...and I've started up a while loop to monitor the situation:

while : ; do echo $(date) $(xwininfo -tree -root | wc -l); sleep 
$[60*60*4]; done

...but is there a better diagnostic to run?

My intuition is saying that once I hit the limit, the number of possible 
concurrent windows drops rather fast - and may get worse each time I get 
the "Maximum number of clients reached" error.

Could it be a file descriptor (socket?) leak?

On Wed, 26 Dec 2007 10:12:30 -0800, Dan Stromberg wrote:

> ISTR that the message I'm getting is "maximum number of clients reached
> 255".
> 
> Also, shouldn't xlsclients tell me if I have ghost windows?  If not, is
> there some other way I should be checking?
> 
> Thanks!
> 
> James Weatherall wrote:
>> Dan,
>>
>> What makes you think you're hitting a client limit?  Have you check to
>> make sure that the X applications you're using are actually quitting
>> when you think they are?
>>
>> Cheers,
>>
>> --
>> Wez @ RealVNC Ltd
>>  
>>  
>>
>>> -----Original Message-----
>>> From: vnc-list-admin "at" realvnc.com
>>> [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Dan Stromberg Sent:
>>> 21 December 2007 21:08
>>> To: vnc-list "at" realvnc.com
>>> Cc: Dan Stromberg
>>> Subject: Maximum number of clients reached?
>>>
>>> I keep bumping up against the maximum number of clients. Sometimes
>>> I'll have as few as 38 windows open (according to xlsclients), and
>>> still I hit the limit.
>>>
>>> I like to log in, and stay logged in a long time, leaving lots of
>>> windows open so I can flip back to the quickly and easily using a
>>> large pager in fvwm2.  Because I keep hitting this limit, I have to
>>> kill all my windows and start over from time to time.  Perhaps in a
>>> windows environment that's unsurprising, but in the Linux world, it's
>>> weird.
>>>
>>> I've had the same problem for a long time - across multiple OS
>>> upgrades.  I'm currently having the problem with the openSUSE 10.3
>>> version of Xvnc, which is based on RealVNC 4.1.2.
>>>
>>> Is this a known problem in vanilla RealVNC 4.1.2?  Is there a fix or
>>> workaround - like perhaps increasing the limit from 255 to 65535 or
>>> something?  That way, I could at least leak clients longer.  :)
>>>
>>> If it matters, the openSUSE Xvnc has 1301 lines of patches applied to
>>> it, relative to the upstream sources.  It's not massively modified,
>>> but not minisculely either.
>>>
>>> Thanks!
>>> _______________________________________________ VNC-List mailing list
>>> VNC-List "at" realvnc.com
>>> To remove yourself from the list visit:
>>> http://www.realvnc.com/mailman/listinfo/vnc-list
>>>
>>>
>>>     
>>
> _______________________________________________ VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list