I guess you could change the DisplaysPerHost=1 to DisplaysPerHost=2 in gdm.conf
Date: Tue, 14 Jan 2003 09:59:10 -0600 (CST) From: "Jeff Roberts" <[EMAIL PROTECTED]> Hey guys, I'm sure some of you have seen this error message before: XDMCP fatal error: Session declined maximum number of open sessions from your host reached I have gotten it here and there, and while sometimes irritating, if I shut down the terminal and wait a few minutes the terminal will come back up. However this morning, we had a power outtage in an office where we have a few terminals, and one of them refused to come back up until I restarted the terminal server. I know that it has something to do with the server still thinking that particular machine is still active on an old session, but I'm not sure what to do to kill the old session, short of rebooting the server. We are using gdm on redhat 8 Is there anyway to reset the old session, or if I switch to xdm would it solve the problem? I see that a few other people have posted this same problem, but I never saw a clear answer in the archives. Thanks, Jeff ------------------------------------------------------- This SF.NET email is sponsored by: A Thawte Code Signing Certificate is essential in establishing user confidence by providing assurance of authenticity and code integrity. Download our Free Code Signing guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
