Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 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
<== Date ==> <== Thread ==>

Subject: Re: caRepeater not found when starting ioc under procServ
From: Maren Purves <m.purves@eaobservatory.org>
Cc: EPICS tech-talk <tech-talk@aps.anl.gov>
Date: Wed, 26 Apr 2017 10:07:10 -1000
There is a /etc/init.d/caRepeater (at least that's where ours is now) that was written
by Janet Anderson over 20 years ago, updated by Andrew Johnson - and then
later locally by us. If you put that on each host that _may_ need it (it isn't exactly
a resource hog) you don't have to start any such thing in the iocs.

All needed paths and other environmental variables are specified in it - you may
of course have to customize one or the other.

Maren

On Wed, Apr 26, 2017 at 9:54 AM, Bruce Hill <bhill@slac.stanford.edu> wrote:
We avoid that problem by launching one procServ running caRepeater  on each host using the full path.
That way we don't rely on the ioc launching caRepeater and don't lose caRepeater if the first ioc is down.

If you want to set PATH or other env for your ioc st.cmd you can do it in the script that launches your procServ.
I'm not familiar w/ procserv-initd, but you could probably set PATH there if you want.   We launch our ioc's
from a custom /etc/init.d/ioc that sources other scripts to set EPICS_CA* and other env vars.

Regards,
- Bruce

On 4/26/2017 11:35 AM, Hinko Kocevar wrote:
Hi,

Maybe using full path to the caRepeater would solve it?

Otherwise, I think using a config file that specifies the path and sourcing it in initd script might do the trick, too. As far as I know that is what any other initd script would do. 


Thanks,
Hinko

On Wed, 26 Apr 2017 at 20:08, Michael Westfall <mwestfal@gemini.edu> wrote:
Hello,

When I start my soft IOC under procserv using the procserv-initd script, the IOC reports that the caRepeater executable can't be located.

This is surely because the PATH variable is not set right in this case. 


The question is how (or where) do you have to set the PATH variable for processes running under procServ using the procserv-initd script?


Thanks...


--
Mike Westfall
Control Systems Software Engineer


--
.. the more I see the less I believe.., AE AoR



References:
caRepeater not found when starting ioc under procServ Michael Westfall
Re: caRepeater not found when starting ioc under procServ Hinko Kocevar
Re: caRepeater not found when starting ioc under procServ Bruce Hill

Navigate by Date:
Prev: Re: caRepeater not found when starting ioc under procServ Bruce Hill
Next: Re: Control System Studio: Final value can't be of type PVANTNDArray Bruno Martins
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
Navigate by Thread:
Prev: Re: caRepeater not found when starting ioc under procServ Bruce Hill
Next: Re: caRepeater not found when starting ioc under procServ Ralph Lange
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
ANJ, 26 Apr 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·