1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Killing caRepeater on Windows 10 |
From: | "Bommannavar, Arun S. via Tech-talk" <[email protected]> |
To: | "Rivers, Mark L." <[email protected]> |
Cc: | Tech Talk <[email protected]> |
Date: | Tue, 14 Jan 2020 12:32:18 +0000 |
Does “netstat” show the UDP 5065 being used when caRepeater shows up in “tasklist” ? Dr. Arun Bommannavar XSD, HPCAT, Sector 16 Argonne, IL 60439 TEL : (630) 252-0497 Email:
[email protected] [The Maintainer's Motto] →
If we can't fix it, it ain't broke. From: Tech-talk <[email protected]> On Behalf Of
Mark Rivers via Tech-talk 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 |