[FreeNX-kNX] FreeNX "maintenance" scripts
Jonathan Chen (jonachen)
jonachen at cisco.com
Thu Jun 30 22:10:13 UTC 2005
Hey all,
Just curious if anyone has any "maintenance" scripts already written to
handle FreeNX/X11 lock files left in /tmp dir and FreeNX nxserver --list
"ghost" sessions.
This is something I've been discovering using FreeNX 0.3.1...
If somehow a user tries to log onto a server and then suddenly decides
to not connect in the middle of a login, FreeNX will sometimes have
/tmp/.nX###, /tmp/.X1### and /tmp/.X11-unix/1### left behind. Leaving
any of the lock files behind that it would cause "agent blocked"
messages in /var/log/nxserver.log.
Then sometimes when a user uncleanly logs off or just a sudden
disconnect from a FreeNX session, the FreeNX db would leave a "ghost"
session that causes a new user not able to either log in or use that
display #.
This is what I have been discovering we put FreeNX into production.
-Jonathan
More information about the FreeNX-kNX
mailing list