I'm running Mandrake 9.2 on servers in a retail environment. The sales counters are running X through thin clients. Since this is a closed network I've set up the thin clients up to be XDMCP servers on broadcast. Every week or so I get the error that maximum number of XDMCP connections has been reached and the Mandrake...er Mandriva server won't allow the thin client to attach.

This error seems to show up during the logging changes at 4:02am every morning. Also I should note that each of the stores that have this issue have 3 or more X windows logins on the system. The places with just 2 don't seem to have this problem or haven't had this problem yet.

My maximum number of XDMCP clients is set to 32 in the gdm.conf so I have plenty of connections...or so I thought. Apparently when the system is switching over the logs it's firing up X-sessions to do the moves and not releasing them when it's completed. Any suggestions for tuning this problem?

I would hope logs are in no way handled by use of X sessions. That would, quite frankly, make no sense. How are you handling log rotation?

It's weird it's set up by the defaults. The only reason I bring up the log rotation is that the X error occurs most frequently concurrent with the log rotation processes. It could be a coincidence on 3 different systems all having the same issues but I don't think it is. And quite frankly I can't for the life of me figure out why copying a set of log files and zipping them and touching new empty files would require 32 X client processes either. Heck there aren't even that many logs.