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: PV name change and autosave |
From: | Tim Mooney <[email protected]> |
To: | Emmanuel Mayssat <[email protected]> |
Cc: | [email protected] |
Date: | Fri, 7 Jun 2013 14:47:11 -0500 (CDT) |
From: "Emmanuel Mayssat" <[email protected]>
To: [email protected]
Sent: Friday, June 7, 2013 12:30:40 PM
Subject: PV name change and autosave
To be compliant with a naming convention, changing the name of a PV should be a "trivial" operation.That is true particularly for PV that are not used in higher level software (seq, feedback, info chart, etc)Let's focus just for a moment on autosave.Can the req file, generate itself "automatically"?dbgrep *O > myfile.reqcould do the trick, if you naming convention appends "O" at the end of the output records.Unfortunately redirection on dbgrep doesn't work since 3.14.10...Do redirection on dbgrep work in 3.14.12.3+ ?Of course the req file can be generated manually starting with dbl * > dblist.rawHow do you generate you req file after a simple PV name change?--Emmanuel