Experimental Physics and
Industrial Control System

On 28.11.2012 17:38, Andrew Johnson wrote:
>> Of course, that was my first thought, too. However, what happens if
>> this caRepeater for some reason dies - wouldn't the RT-IOC try to
>> spawn a new one (now running under SCHED_FIFO)? This could lead
>> to ugly spurious real-time violations.
> True, unless we had some kind of wrapper that would restart the caRepeater.

We have one.
procServ can run almost anything as child process: IOCs, caRepeaters, CA
Gateways, ParseCASW (the annotated beacon anomaly checker).....
It (among many other things) offers auto-restart.

~Ralph

References:

posix osiSpawnDetachedProcess inherits scheduling policy + priority Till Straumann

Re: posix osiSpawnDetachedProcess inherits scheduling policy + priority Andrew Johnson

Re: posix osiSpawnDetachedProcess inherits scheduling policy + priority Till Straumann

Re: posix osiSpawnDetachedProcess inherits scheduling policy + priority Andrew Johnson

Navigate by Date:

Prev: Re: posix osiSpawnDetachedProcess inherits scheduling policy + priority Andrew Johnson

Next: Agilent N1912A Szalata, Zenon M.

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: Re: posix osiSpawnDetachedProcess inherits scheduling policy + priority Andrew Johnson

Next: Data acquisition for ICP accelerometers Matt Rippa

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