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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: How to get a list of all available PVs |
From: | Michael Davidsaver <[email protected]> |
To: | [email protected] |
Date: | Mon, 17 Dec 2012 12:29:41 -0500 |
On 12/17/2012 6:14 AM, Carlos Pascual wrote:
Ronaldo, Thanks for the tip. I looked at channel finder docs and I gather that somehow one needs to manually add the info to the directory itself. I mean, that the channel finder cannot by itself discover available PVs. If possible I would like to avoid such requirement of manually creating the database.
At NSLS2 the process to automatically keep channelfinder up to date is this: Each IOC init script ends with
dbl > records.dbl system "cp records.dbl /cf-update/$HOSTNAME.$IOCNAME.dbl"
The two variables are set from the environment by a shell wrapper script for Linux systems, and manually for RTEMS systems.
The location /cf-update is exported from an NFS server and mounted by all IOC host systems. The NFS server has a process which monitors for new/updated files in this directory.
http://channelfinder.hg.sourceforge.net/hgweb/channelfinder/python.channelfinder.api/file/f0d7b9404db3/cf_monitor.shWhen a record list is updated the cf-update-ioc script is run which handles sending the new information to the channelfinder service.
Once the NFS server has been setup this works fairly well. The ongoing problem is to ensure that all IOCs create a record listing file. Also, by design the cf-update-ioc script only adds records, so it a maintenance task to periodically purge orphaned entries.
Michael