Re: Killing caRepeater on Windows 10

[Michael Davidsaver via Tech-talk <tech-talk@aps.anl.gov>]

Maybe the answer here is for caRepeater to borrow a page from *NIX daemons and "cd /" after startup?
(or rather "cd C:\")


On 1/13/20 3:52 PM, Mark Rivers via Tech-talk wrote:
> Folks,
> 
>  
> 
> One of the hassles with Windows is that you cannot delete or replace an executable or dll if any process is using it.  If an EPICS client or IOC is run on Windows it will launch a caRepeater process that runs in the background.  If you want to update your EPICS installation you must kill that caRepeater process before you can do so.
> 
>  
> 
> In Windows 7 I found that the caRepeater process always showed up in Task Manager, so it was easy to find and kill.
> 
>  
> 
> In Windows 10, however, caRepeater does not show up in the Task Manager, even though it is running and the executable file cannot be deleted.
> 
>  
> 
> I found a couple of solutions to finding and killing caRepeater without rebooting.
> 
>  
> 
> 1)      Use “tasklist” to find the PID of caRepeater
> 
> tasklist /FI "imagename eq caRepeater.exe"
> 
>  
> 
> will show the PID of caRepeater, which "taskkill" can then kill.
> 
>  
> 
> 2) Microsoft has a nice "Process Explorer" application that is a more powerful version of Task Manager.  You can find it with Google and download it.
> 
>  
> 
> caRepeater shows up there, while it does not show up in Task Manager.  Note that in this case it is nested under PointGreyApp.exe, which is my IOC.
> 
>  
> 
>  
> 
> I suspect perhaps the reason it is not showing up in Task Manager is that Task Manager may only be showing nested processes 2 deep, rather than 3 deep?
> 
>  
> 
> Mark
> 
>  
>