> If is running, then stop it, then start it, ensures a new
> copy is running.
Note that if you abruptly stop a ca repeater that ca clients have become
dependent on then these clients will be left without ca repeater
functionality.
Jeff
> -----Original Message-----
> From: Billy R. Adams [mailto:[email protected]]
> Sent: Monday, June 28, 2004 1:34 PM
> To: Simon Rees
> Cc: EPICS Tech-Talk
> Subject: Re: caRepeater working practices
>
> Simon,
>
> I can't answer the why or if should be needed.
>
> Here is how I start it, if needed, in my main C-program.
> (C-code) to automatically detect if caRepeater is already running. If
> is running, then stop it, then start it, ensures a new copy is running.
> If not running, then start it.
>
> I have to start caRepeater on a hybrid system where I have EPICS
> 3.14.5 on a Linux PC and EPICS 3.1.2 on the IOCS used in transitioning
> to EPICS 3.14.5.
>
> /* ============================================================
> */
> /* Start "caRepeater" for EPICS-3.14.x on Linux
> 06-05-03 07-10-03 [email protected]
> 1. If running, then first kill "caRepeater"
> 2. Start "caRepeater" */
> int returnCode;
> printf ("\n");
> returnCode = system ("date");
> returnCode = system ("(ps -elf | awk '{print $15,$4}' | grep
> caRepeater) ");
> if (returnCode == 0) {
> fprintf (stdout, "Killing old running 'caRepeater'\n");
> returnCode = system ("(ps -elf | awk '{print $15,$4}' | grep
> caRepeater) | kill -9 `aw
> k '{print $2}'`");
> }
> fprintf (stdout, "Starting
> '/usr/local/epics/bin/linux-x86/caRepeater &'\n");
> returnCode = system ("/usr/local/epics/bin/linux-x86/caRepeater
> &");
> returnCode = system ("(ps -elf | awk '{print $15,$4}' | grep
> caRepeater) ");
> /* ============================================================
> */
>
>
>
> Simon Rees wrote:
>
> > Dear all
> >
> > Please excuse the naivety of this question but I am
> > just getting to grips with EPICS here at the Isaac Newton
> > Group of Telescopes. I have searched through the EPICS
> > documentation and so far haven't found any definitive
> > pointers.
> >
> > Is it considered standard practice to start a caRepeater daemon
> > at machine boot time for any machine on which you might want to
> > run CA clients ? (If there are many potential machines this might
> > be a bit of a burden to the system administrators).
> >
> > Alternatively, do most people just allow the first client
> > which runs on the machine after reboot to spawn the caRepeater
> > and for all subsequent clients on the same machine to use it ?
> >
> > Here at ING we are running with R3.13.1; our clients typically
> > run on Solaris 5.9 workstations.
> >
> > Many thanks
> >
> > Simon Rees
> > Isaac Newton Group of Telescopes
> >
> >
> Billy Adams <mailto:[email protected]>
>
> Sverdrup NASA/Langley ROME Group
> Assigned to: Research Facilities Branch of
> Research Facilities Services Competency
> Building 1251, Room 126D
> NASA Langley Research Center
> Hampton, Va. 23681-2199
> Phone 1-757-224-7858 Fax 1-757-224-7870
>
- References:
- Re: caRepeater working practices Billy R. Adams
- Navigate by Date:
- Prev:
Re: caRepeater working practices Brian McAllister
- Next:
Re: caRepeater working practices Maren Purves
- 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: caRepeater working practices Billy R. Adams
- Next:
Re: caRepeater working practices Brian McAllister
- 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
|