I too am hurting...I've been having a similar problem on terminals that get powered off and then powered on quite frequently. One terminal refused to reconnect for three days(!). I've also got the complication(?) that I'm not running ddns updating on my server and don't use DHCP to send hostnames to my terminals - I just map any possible auto-assigned IP addresses to a hostname in /etc/hosts and dhcp just gives them enough info to boot up.
The only real info that I've dug up suggests that I increase the maximum session count in gdm.conf...hasn't seemed to help me much. Sometimes by rebooting the terminal a few times the problem clears and the login screen becomes available again. This is the only tangible problem that I've encountered while running LTS on RH 8.0 (tho' mozilla occasionally hogs 100% of cpu time.....glad I'm running a dual cpu system :o) ) What was the old thread you started Jeff? (me being lazy and not wanting to hunt for it) Any ideas anyone? Anyone else seeing this problem/found a fix? David Mummery I feel your pain. There is an old thread on this topic that I believe I started. Usually a station recovers in about five minutes from an unclean shutdown. However I have had to resort to changing the stations hostname in dns and dhcp to recover it without bringing down the server. Surely we are not the only one who've experienced this problem. -Jeff > Howdy everybody, > > Probably a newbie question, but. If a workstation > is reset or powered off/on while a user session is > in progress, the server doesn't seem to care. > > The workstation freezes saying, "XDMCP fatal error: > Session declined Maximum number of open sessions from > your host reached," and it looks like nothing can bring > it back to life until the user gets logged out by PAM, > and the watchdog cron job kills all the processes > run by that user. > > What's wrong: the user stays logged in, while not > actually working, -- for up to 6 minutes in my > experiments, -- and they pay for every minute of > it. Also, in other environments, this could knock > a workstation out of business until the sysadmin > comes back and hunts the offending processes down > manually. > > What I want: ideally, smooth continuation of the > user's session. But an immediate (and clean) logout > will do as well. > > Any existing solutions? Ideas? FM to R? > > TIA > > -- > Killing a spammer doesn't affect your karma. -- ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _____________________________________________________________________ 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.freenode.net
