[vizstack-users] Vizstack issue - leaving behind /tmp/.X... files

[<Pet...@cs...>]

Hi,

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'm using a late SVN version of Vizstack with TurboVNC 1.0 on Ubuntu 10.04.  Any ideas?

Cheers,
Peter
  

Peter Tyson
CSIRO IM&T - Advanced Scientific Computing
Gate 5 Normanby Road 
Clayton Vic 3168 
Ph +61 3 9545 2021