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: CaSnooper Update? |
From: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "Johnson, Andrew N." <anj at anl.gov>, "Murray, Doug" <drm at slac.stanford.edu>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 6 Dec 2023 17:54:49 +0000 |
> However I suspect it might be easier to start from scratch (I'd recommend using the PVXS API) to implement a separate pvSnooper program. I agree. For what it’s worth, the core-pva java library already contains a PVA search monitor that does a lot of what caSnooper does for Channel Access. It’s not much code, see
https://github.com/ControlSystemStudio/phoebus/blob/master/core/pva/src/main/java/org/epics/pva/server/PVASearchMonitorMain.java Example Usage: $ ./pvasearchmonitor -h USAGE: pvasearchmonitor [options] Options: -h
Help -p <seconds>
Update period (default 10 seconds) -1
Update once, then quit -v <level>
Verbosity, level 0-5 Waits for the specified period, then prints information about received search requests. Output of running it while calling “pvget Demo Test AnotherPV” in another window: $ ./pvasearchmonitor -p 10 -1 Monitoring search requests for 10 seconds... Count Name
Last Client
Age 36 Demo
/10.1.58.230:50842
2 sec 36 Test
/10.1.58.230:50842
2 sec 36 AnotherPV
/10.1.58.230:50842
2 sec Done. For a C++ implementation I agree that PVXS would be a good starting point. Thanks, Kay |