Menu
▾
▴
#14 Uncleaned /tmp/.X files from TurboVNC
Reported by Peter Tyson on the mailing list :
I've been seeing an issue with Vizstack where at times /.X*-lock and /tmp/.X11-unix/X* files are being left behind from VNC sessions. The files relating to the 3D X servers are always cleaned up, the files in question are from VNC sessions. This seems to have only occurred when a user has terminated their session by closing the SSH application (usually Putty on Windows) or shutdown their PC/logged out with a session still active rather than pressing cntl-c to take them back to the prompt. The job has always been removed from the SLURM queue in these cases. This problem is intermittent although it has been happening quite frequently. Having these lock files left behind causes quite a problem of course as Vizstack will often want to use that display number for the next VNC session on that particular node.
I am trying to fix this.
vs-Xv has code to do cleanup on termination. The cleanup code sends the TERM signal to the VNC process, waits for it to exit, and then cleans the files in /tmp.
Peter says that only the log files remain, but the VNC and vs-Xv processes are not around. I feel that the apps are catching the TERM signal, but don't have sufficient time to wait for the VNC server to exit before doing the cleanup. So, I have now added code to remove the tmp files before trying to kill the process.
I have asked Peter to test with this (ChangeSet 355). If he doesn't notice the problem for many days, then maybe I'll consider this change successful.