Subject: Re: x2goclient terminates with "WARNING: failed to kill process group
 '<pid>': No such process
To: Seth Galitzer <sgsax@ksu.edu>, 1166@bugs.x2go.org
References: <3d8e2b63-3137-4170-7681-8cebf1df2d64@ksu.edu>
From: Mihai Moldovan <ionic@ionic.de>
Message-ID: <ee6a77dd-074a-8ac3-987e-f8a736282218@ionic.de>
Date: Tue, 28 Mar 2017 14:03:11 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <3d8e2b63-3137-4170-7681-8cebf1df2d64@ksu.edu>
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="xBKITppcdLM2K2HqNvx42Lx9dBCbNBUop"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--xBKITppcdLM2K2HqNvx42Lx9dBCbNBUop
Content-Type: multipart/mixed; boundary="UaeAaWRXABmEkrxkHFpV10RjR95b12aL2";
 protected-headers="v1"
From: Mihai Moldovan <ionic@ionic.de>
To: Seth Galitzer <sgsax@ksu.edu>, 1166@bugs.x2go.org
Message-ID: <ee6a77dd-074a-8ac3-987e-f8a736282218@ionic.de>
Subject: Re: x2goclient terminates with "WARNING: failed to kill process group
 '<pid>': No such process
References: <3d8e2b63-3137-4170-7681-8cebf1df2d64@ksu.edu>
In-Reply-To: <3d8e2b63-3137-4170-7681-8cebf1df2d64@ksu.edu>

--UaeAaWRXABmEkrxkHFpV10RjR95b12aL2
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Control: close -1
Control: tag -1 not-a-bug

On 27.03.2017 08:58 PM, Seth Galitzer wrote:
> Package: x2goclient
> Version: 4.1.0.0 and 4.1.0.1
>=20
> When exiting x2goclient, after a pause of about 2 seconds, the following=
=20
> message is displayed to stderr:
> WARNING: unable to send SIGTERM to process group '<pid>': No such process
>=20
> About 10 more seconds later, the following message is displayed to stderr:
> WARNING: failed to kill process group '<pid>': No such process
>=20
> In some cases, the first message is not displayed, but the second one=20
> always is after about 10-12 seconds. The pid is the same in both message.
>=20
> This seems to only affect 4.1.x clients. 4.0.x clients do not seem to=20
> have this behavior.

Most of the time, that's perfectly fine and nothing to worry about.

It merely means that x2goclient and its child processes exited cleanly befo=
re
the cleanup process could kill them.

If you should ever see stray x2goclient processes left *after* these messag=
es,
then that's something to worry about.


Mihai


--UaeAaWRXABmEkrxkHFpV10RjR95b12aL2--

--xBKITppcdLM2K2HqNvx42Lx9dBCbNBUop
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJY2lEHAAoJEB/WLtluJTqH+FwP/j1GGEIo12htpsEsvvYPdwgS
mUEfHQ3b4Way0Tl5DybmyrOtChkXO5mVBnxbzkBXTNdJ+LQk/6UZXv9R2617wW8A
s9Wv+iUAqTfkW2JpjZsQj7h6Ljw0zaADYAlr3pZPBDW8WHavxafQCxkinIC/Z2EJ
yZVPzuXzG65PaEf12+gjot4HZMG51xcLACSLUUTMzrGdcr6EZibGu3621GJwxmHA
3+GPuoz8Gt2oV1vTjhi9alBan0gLVov5ShLjVCI5V3aLNzDOrSPzotzyD3dgcqpi
0istxXree5tMyRy3FrzW5/toZ3UndIQqGZ+0QKiRZji+S4RIuBw5M46ry87SoRXQ
aSMy62hG+I8bdffHb0FThibzeyufpqCY7sJRGjeZpm/eDYl9odFc9TwhVSXyYtp/
dqi0nytudq7yIFZElImEt9KlvMKXG7OPV89blcZC+B0WnGDS7AGNteAZnSnc8nyp
rVabfFSvV0E+vRkRl+1J6OO2E7eDlkdZE4s5Bcs4OIiwL7ngICclr6dJYs+SoI0i
GbuAvpCwpwnDdJt+U9TmV2k2ew8iEfKmunhXJqbOzNEQ8MASc1cZ1v8m5xDZr4fl
D+jmzSxjLo3WvsIEQtXrvVenmy+20MIC/vlm+gFy6ZP2cz+FYzkXwNIqA+hGFKUV
IpHsvZU3onYuY+RGV+JI
=oMyv
-----END PGP SIGNATURE-----

--xBKITppcdLM2K2HqNvx42Lx9dBCbNBUop--