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 <[email protected]> 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