I have one user with a Windows Vista laptop who has a particular problem: He has a session open, then suspends his laptop by closing the lid, but without first terminating his nx client. Later, he unsuspends his laptop. At this point his nx client pops up with the dialog saying that the connection to server was lost, and do you want to terminate the session? He selects Yes. Then he starts up the nx client and logs in, expecting to resume his existing session, but instead he gets a new session. His old nxagent is still running, but he now has a second, new nxagent process. This happens even though SESSION_USER_LIMIT is set to 1. The old nxagent is lost, in the sense that it does not show up in "nxserver --list" and there is no way to login to it. Aside from that, though, the old nxagent is apparently running fine. There does not appear to be anything wrong with nxagent itself, it looks more as if freenx is somehow losing track of the existing session. Has anyone seen behaviour like this? Where does freenx keep its list of the currently active nxagents, and how could it become confused in this way? -- Mario Becroft ________________________________________________________________ Were you helped on this list with your FreeNX problem? Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: http://www.nomachine.com/kb/ ________________________________________________________________ FreeNX-kNX mailing list --- FreeNX-kNX@kde.org https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________