Experimental Physics and
Industrial Control System

Ø  When I use caget, it appears both under Details *and* under Users on my Windows 10 system.

 

What version of caget are you using?

 

I just tested on my system with caget from base 7.0.3.1 and I don't see that.

 

Here I kill caRepeater, run caget, and then see that caRepeater is indeed running:

 

****************************

J:\epics\devel\dxp>taskkill /f /im caRepeater.exe

SUCCESS: The process "caRepeater.exe" with PID 9896 has been terminated.

 

J:\epics\devel\dxp>h:\epics\base-7.0.3.1\bin\windows-x64-static\caget 13IDA:m1

13IDA:m1                       -0.250184

 

J:\epics\devel\dxp>tasklist /fi "imagename eq caRepeater.exe"

 

Image Name                     PID Session Name        Session#    Mem Usage

========================= ======== ================ =========== ============

caRepeater.exe                8576 Console                    1      3,640 K

****************************

 

When caRepeater is running this is what I see in Task Manager/Users and /Details.

 

 

 

 

I don’t see caRepeater in either screen.

 

It seems that either caget has changed behavior, or something is configured differently on your Windows 10 system from ours?

 

Mark

 

 

-----Original Message-----
From: Engbretson, Mark S. <[email protected]>
Sent: Tuesday, January 14, 2020 8:26 AM
To: Mark Rivers <[email protected]>
Subject: RE: Killing caRepeater on Windows 10

 

When I use caget, it appears both under Details *and* under Users on my Windows 10 system.

 

-----Original Message-----

From: Tech-talk <[email protected]> On Behalf Of Mark Rivers via Tech-talk

Sent: Tuesday, January 14, 2020 6:20 AM

To: Žiga Oven <[email protected]>

Cc: tech-talk <[email protected]>

Subject: Re: Killing caRepeater on Windows 10

 

 

> I believe that the other option to find this process in the Windows 10

> Task Manager is under the 'Details' tab (which to me looks like the

Windows 7 'Processes' tab) .

 

No, unfortunately that is where I expected to find it, but it does not appear there if caRepeater was started by another EPICS application.  It did appear in the Processes tab in Windows 7, but does not appear in the Details tab in Windows 10.

 

Mark

 

 

________________________________

From: Tech-talk <[email protected]> on behalf of Žiga Oven via Tech-talk <[email protected]>

Sent: Tuesday, January 14, 2020 2:00 AM

To: [email protected]

Subject: Re: Killing caRepeater on Windows 10

 

Hi Mark,

 

I believe that the other option to find this process in the Windows 10 Task Manager is under the 'Details' tab (which to me looks like the Windows 7 'Processes' tab) .

 

Best regards,

 

Žiga

 

On 14. 01. 2020 00:52, 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.

> 

> [cid:[email protected]]

> 

> 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

> 

>