On Wed, 2006-08-03 at 16:02 -0600, Les Mikesell wrote: > I've had an assortment of problems with sessions lingering > that should have been terminated and not being able to > resume sessions that should have been available. I don't > think they are fedora-specific problems but I'd appreciate > any insight - it is great after the connection works. I've seen that, too. I'm not sure what triggers it. The NX client kills the connection, but freenx (that's what I've deployed...not using the commercial NX server yet) fails to clean up the session. It doesn't happen all the time, either. What I've done is set up a cron job that basically runs 'nxserver --cleanup'. That kills all running/failed/whatever NX sessions that have been left behind. It's not ideal since the sessions shouldn't be left behind in the first place, but at least it works. BTW, I've experienced this on CentOS 4 machines. It's definitely not a Fedora specific issue. It's most likely a freenx problem. Try out the freenx 0.5 snapshot. It might work better for you (I haven't tried it yet). Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.15-1.1833_FC4 i686 GNU/Linux 11:26:43 up 4:56, 3 users, load average: 0.82, 0.53, 0.52
