Bug 5194

Summary:	Client should --loop using same process pid, for easy termination
Product:	ThinLinc	Reporter:	Peter Åstrand <astrand>
Component:	Client	Assignee:	Peter Åstrand <astrand>
Status:	CLOSED FIXED
Severity:	Normal	CC:	hean01
Priority:	P2	Keywords:	hean01_tester, prosaic
Version:	4.2.0
Target Milestone:	4.3.0
Hardware:	PC
OS:	Unknown
Acceptance Criteria:
Bug Depends on:
Bug Blocks:	5185

Description Peter Åstrand cendio

2014-06-23 14:30:21 CEST

This is a follow up to bug 3633. Since it is impossible to replace a process image on Windows, one must create a new process, which means you get a new pid. When implementing bug 3633, we decided to use the same approach for UNIX platforms, even though this is not necessary. This means that you cannot terminate the looping client by sending a signal to the original PID, and there's no easy way of finding the new pid. We should change the client so that the original PID is used on UNIX platforms.

Comment 1 Peter Åstrand cendio

2014-06-23 14:32:19 CEST

Tester should test on Linux, Mac and Windows.

Comment 2 Henrik Andersson cendio

2014-09-24 14:44:23 CEST

Verified using ThinLinc client build 4500,

Linux and Mac replaces the process image and the same PID is used while Windows behaves like before, a new PID for each respawn.

Works as expected.