RE: How to know which CA client(IP address) modified a PV

["Mercado, Ronaldo \(DLSLtd, RAL, LSCI\) via Tech-talk" <tech-talk at aps.anl.gov>]

Hi,

 

Thanks for writing.

Sorry for the lack of documentation for pvlogging.

I typed below instructions to use the module based on examples I have seen.

For step 3, I haven’t seen any example use anything other than the default.

Regards,

Ronaldo

 

1. add pvlogging to your lib files, e.g. in xxApp/src/Makefile

 

xx_LIBS += pvlogging

 

2. add pvlogging to your dbd files, e.g. in xxApp/src/Makefile

 

xx_DBD += pvlogging.dbd

 

3. Set up an access file in the startup script.

   The suggested default is 'data/access.acf'

e.g. in st.cmd add

 

asSetFilename "/dls_sw/prod/R3.14.12.3/support/pvlogging/1-3/data/access.acf"

 

 

4. Optional step, load a blacklist in the startup script, e.g.

 

load_logging_blacklist 'SR02J-CS-IOC-01App/data/auto_blacklist'

 

---- example contents for a blacklist file (generated using  iocbuilder) --

Automatically generated, do not edit

SR02J-MO-SERVC-01:FIELD

---- end of example contents --

 

From: LiangChih Chiang <yehnan174 at gmail.com>
Sent: 12 May 2025 03:30
To: Mercado, Ronaldo (DLSLtd,RAL,LSCI) <ronaldo.mercado at diamond.ac.uk>
Cc: tech-talk at aps.anl.gov
Subject: Re: How to know which CA client(IP address) modified a PV

 

I tried caPutLog and succeeded.

Need more time to configure the access security file to restrict what to log.

 

 

I can't find the document of the pvlogging module.

Is there any?

 

 

On Fri, May 9, 2025 at 6:16 PM Mercado, Ronaldo (DLSLtd,RAL,LSCI) <ronaldo.mercado at diamond.ac.uk> wrote:

Hi,

 

I have used pvlogging for this purpose.

 

https://github.com/DiamondLightSource/pvlogging

 

Regards,

Ronaldo

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of LiangChih Chiang via Tech-talk
Sent: 09 May 2025 04:15
To: J. Lewis Muir <jlmuir at imca-cat.org>
Cc: tech-talk at aps.anl.gov
Subject: Re: How to know which CA client(IP address) modified a PV

 

Thanks.

 

caPutLog seems to be a satisfying solution. I will give it a try.

 

The log messages include host information as the following excerpt from the documentation:

 

    The actual log message sent from the IOC has this format:  

    <iocLogPrefix><date> <time> <host> <user> <pv> <change>

 

 

 

 

 

On Fri, May 9, 2025 at 10:58 AM J. Lewis Muir <jlmuir at imca-cat.org> wrote:

On 05/09, LiangChih Chiang via Tech-talk wrote:
> How to know which CA client(IP address) modified a PV in EPICS version 3.14.
>
> I searched and got two methods:
>
> What other methods do you use or recommend?

Haven't used it myself, but there's caPutLog:

  https://github.com/epics-modules/caPutLog

Lewis

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom.