On Tue, Feb 20, 2018 at 12:54:26PM +0100, Wolfgang Schweer wrote: > Seems to be X2Go Bug #1171 Create wtmp entry for x2go sessions > > See: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1171 After testing x2goserver on a Stretch system I noticed that X2Go sessions can be detected reliably due to some command using a param string containing 'X2GO'. This change would work around the x2go bug running the killer cron job only in case an X2Go session isn't detected: --- a/cron.hourly 2014-06-11 11:15:55.000000000 +0200 +++ b/cron.hourly 2018-02-22 19:42:36.419963949 +0100 @@ -1,3 +1,3 @@ #!/bin/sh -if [ -x /usr/sbin/killer ] ; then /usr/sbin/killer; fi +if [ -x /usr/sbin/killer ] && [ $(ps ax | grep X2GO | wc -l) -le 1 ] ; then /usr/sbin/killer; fi Mike: could you test and give some feedback? Wolfgang
Attachment:
signature.asc
Description: PGP signature