Subject: rather a post-cleanup issue in x2gocleansessions

From: Mike Gabriel <[email-masked]>
Date: Thu, 02 Oct 2014 20:58:55 +0200

Control: reassign -1 x2goserver
Control: retitle -1 NX socket cleanup post-session
Control: severity -1 wishlist

Hi,

there was more insight on IRC which turns this bug into a feature request for x2gocleansessions:

8:19 < bigfoot-> it seems the aforementioned #1 reproducer killed his nxagent via kill -9.  could 
                  this be the reason that his /tmp/.X* stuff wasn't cleaned up?  shouldn't 
                  x2gocleansessions clean this up anyways?
18:22 < bigfoot-> regarding your patch, as on my system actual files (/tmp/.X50-lock, 
                  /tmp/.X11-unix/X50) are used instead of this "abstract socket" stuff, I guess it 
                  doesn't have anything to do with my problems, right?
18:22 <@sunweaver> sure, that can be the reason!!!
18:23 <@sunweaver> kill -9 does forbid any sort of callback, so socket file removal does not 
                   happen....
18:23 < bigfoot-> that I definitely do understand, but what is x2gocleansessions there for then?

--> x2gocleansession should check if X<disp> socket files in /tmp/.X11-unix have got cleanly removed on nxagent shutdown and if not it should handle the post-session cleanup of those socket files.

Mike

-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976148

GnuPG Key ID 0x25771B13
mail: [email-masked], http://das-netzwerkteam.de