Hi Wolfgang, On Do 22 Feb 2018 20:02:31 CET, Wolfgang Schweer wrote:
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=1171After 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; fiMike: could you test and give some feedback? Wolfgang
This is at most a dirty work around. The killer command wipes x2goagent hourly and this must be prevented in killer itself somehow.
With the above patch you disable killer system-wide once at least one X2Go Session is running on the host. Not the right approach.
Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
Attachment:
pgp1F6iWOrx2Y.pgp
Description: Digitale PGP-Signatur