Subject: |
dynamically remove PV's from excas? |
From: |
Benjamin Sailer <[email protected]> |
To: |
EPICS Tech-Talk <[email protected]> |
Date: |
Fri, 1 Aug 2003 19:21:41 +0200 (CEST) |
Hello all,
using R3.14beta2 cas library I was trying to create a Server that
dynamically creates PVs (serving as a parameters that the server
itself can get from another source). Up to now, every time when
I received the query for a new PV, the cas checks whether it conforms
to a naming convention and - if so - creates a PV that can be used
to transfer the parameters. But as those are allocated dynamically,
the memory consumption of the server would grow to infinate if the
server is running all the time, so I was wondering whether I could
remove PVs once used. I tried this and failed, but I'm not sure
whether this was due to wrong programming on my side. Is there some
caching of parameters that could fail if I give a pointer to my
parameter as a return value of
pvAttachReturn pvAttach(const casCtx &ctx, const char *pPVName);
and after some time calling a 'delete' for this pointer. I was thinking
of something like
<snip>
while (aitTrue) {
fileDescriptorManager.process(SCAN_INTERVAL);
cas->expireParams(EXPIRE_INTERVAL);
}
</snip>
in main() where cas->expireParams() looks for parameters unused
and removes them from the parameter list that is checked on every
pvExistReturn pvExistTest(const casCtx &ctx, const char *pPVName);
(I really don't state this is not working due to the cas library,
I just want to rule out that this can be the source of my problem).
Thanks
Benjamin
--
*****************************************************************
Benjamin Sailer
eMail: [email protected]
*****************************************************************
Disclaimer: This signature has been generated automatically and
does not reflect my opinion at all.
-- Benjamin Sailer
Graduate students and most professors are no smarter than undergrads.
They're just older.
- Replies:
- RE: dynamically remove PV's from excas? Jeff Hill
- Navigate by Date:
- Prev:
puzzling "Record Type does not exist" message Michael Borland
- Next:
Re: Problem with static build on Linux Robert Soliday
- 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
- Navigate by Thread:
- Prev:
puzzling "Record Type does not exist" message Michael Borland
- Next:
RE: dynamically remove PV's from excas? Jeff Hill
- 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
|