On Thu, Aug 9, 2012 at 10:00 AM, johnw <[email protected]> wrote: > I run the command "systrace chrome", then close the chrome, > after that I still can see the xsystrace process here. > why the xsystrace process do not follow the systrace process exit?
Because it's much more efficient to have a persistent process that handles all the approvals for all the systrace processes on the system going forward and having an extra X client that hangs around blocked and doing nothing costs, well, almost nothing. If the small amount of memory/swap that that consumes bugs you, then set the xsystrace.timeout resource in your X server to some non-zero value...but beware that that timeout also limits your responses to systrace queries... > is it normal? Yes. Philip Guenther
