Re: Killing caRepeater on Windows 10

[Matt Newville via Tech-talk <tech-talk@aps.anl.gov>]

On Tue, Jan 14, 2020 at 11:52 AM Kasemir, Kay via Tech-talk <tech-talk@aps.anl.gov> wrote:

> Only if I run the version of caget from this directory does it show up in the Task Manager.  If I run any other version it does not show up.

For what it's worth, on Linux the caRepeater process runs as a child process of for example camonitor.

Start first camonitor, and it starts a caRepeater.

End that camonitor via Ctrl-C, and the child caRepeater process also quits.

But that is not true for all CA processes.   `caget  XXX` will start caRepeater if it is not running, and caRepeater will not quit when caget exits normally.  

If the camonitor process is killed with `kill -9 PID`, the caReapeter it has launched will remain running.

Is there a similar child/parent process hierarchy on windows?

Do those different cases that you see result in the same child process tree?

That might determine how/where/under which name the caRepeater shows up in task listings.

--Matt Newville