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: Among the things for which I wish... |
From: | Rolf Keitel <[email protected]> |
To: | Andrew Johnson <[email protected]> |
Cc: | tech_talk <[email protected]> |
Date: | Mon, 10 Nov 2003 17:58:31 -0800 |
Pete R Jemian wrote:This is actually available from DESY. We have been using this for several years now to log all CA activity in our system through the IOC log server.
[1] A tracing mechanism in to find out which host/user last modified this PV. Yes, that will take additional memory. When trying to locate some aberrant client, this is most valuable. Also, useful when trying to identify which user thought we had a new d-spacing in our monochromator (for example).
.......
Another way to do this would be to write some simple logging code for the Access Security write trapping hook. Check the Access Security chapter of the Application Developers' Guide for details.
-- +-------------------------------------------------+ | Rolf Keitel, TRIUMF Tel: (604) 222-7453 | | Group Leader ISAC Controls Fax: (604) 222-7307 | | and Electronics Development | | Vancouver, B.C., Canada | +-------------------------------------------------+