The predecessor to devIocStats was vxStats.  This goes back prior to
3.13.10.  Here's an old tech-talk thread that might get you going.  I
used it for 68060 IOC's.

http://www.aps.anl.gov/epics/tech-talk/2006/msg00055.php

My vxworks machine would complain about "ENOBUFS" and refuse to
accepts additional client connections. I could go months between
problems.


Another idea would be to put a CA gateway between your old IOC and the
network (of clients).  This way, the gateway handles the multiple
clients comm.


-ps

On Mon, Jan 28, 2013 at 12:23 PM, James F Ross
<[email protected]> wrote:
> I don't believe that I am running devIocStats.  It is running a very old
> version of epics: 3.13.10.  Do you happen to know if this is compatible with
> devIocStats?  If so, and I install it, would it require changes to the
> source code or just to the db files to include a memory PV?
> Thanks!
> James
>
> On Mon, Jan 28, 2013 at 11:34 AM, Tim Mooney <[email protected]> wrote:
>>
>> Hi James,
>>
>> Are you running devIocStats?
>> http://www.slac.stanford.edu/grp/cd/soft/epics/site/devIocStats/
>>
>> If so, memory is available as a PV whose value you could record in any
>> number of ways.
>>
>> Tim
>> ________________________________
>>
>> From: "James F Ross" <[email protected]>
>> To: "EPICS Tech Talk" <[email protected]>
>> Sent: Monday, January 28, 2013 10:18:52 AM
>> Subject: memory and vxWorks based IOCs
>>
>>
>> Hello everyone,
>> I suppose this is more a vxWorks question than an epics question, but here
>> is the issue.
>> I've got a VME based IOC running here at STAR that is having memory
>> problems.  Basically we noticed this issue as every 24-48 hours the IOC
>> would lose communication and all GUIs associated with it would go blank.
>> The solution is to re-start the IOC by rebooting the VME, but doing this
>> every day is not a good solution.
>>
>> The epics is running on vxWorks, so I can use the memShow command to show
>> the memory usage at a given time.  I can see that as I open more and more
>> GUIs, the memory fills up.  At least part of the cause of the loss of
>> communication has to do with too many people opening GUIs relating to this
>> IOC at the same time.  However, I am not certain that this is the only
>> problem.
>>
>> What I would like is to track the memory usage over time to see if there
>> is a time component as well as just too many GUIs being opened.  Does anyone
>> know how to do this in vxWorks?  Get it to print its memory usage every
>> minute or so to a log file or something similar?
>> Thanks
>> James
>>
>>
>>
>