Hi,
We're just about to try procServ, in combination with devIocStats, to
restart soft IOCs remotely. As Stephanie says, devIocStats call
epicsExit, which kills the process, and then procServ can automatically
restart the IOC after some time (which is configurable).
Cheers,
Matthew
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Allison, Stephanie
> Sent: 15 April 2009 19:43
> To: Emmanuel Mayssat; [email protected]
> Cc: Mahajan Kirti; [email protected]
> Subject: RE: Remote IOC reboot Was(EPICS for implementation
> of RemoteProcedurecall)
>
> Hi Emmanuel,
>
> There are some device support packages that provide for
> rebooting/restarting an IOC via record. For instance, devIocStats:
> http://www.slac.stanford.edu/comp/unix/package/epics/site/devIocStats/
> provides a sub record that calls epicsExit for soft iocs,
> reboot for vxWorks iocs, and bsp_reset/rtemsReboot for RTEMS iocs.
>
> Stephanie Allison
>
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Emmanuel Mayssat
> > Sent: Wednesday, April 15, 2009 11:26 AM
> > To: [email protected]
> > Cc: Mahajan Kirti; [email protected]
> > Subject: Remote IOC reboot Was(EPICS for implementation of
> > Remote Procedurecall)
> >
> > S,
> >
> > Could you describe your interface (from a user/operator
> > perspective) to
> > your IOC reboot interface? I may actually be interested with that.
> >
> > In short I want to know:
> > Can you reboot/control a remote IOC with the push of a GUI button?
> >
> > --
> > Emmanuel
> >
> > > We use (XML)RPC for some of our control system
> > (specifically to reboot
> > > IOC's under procServ), and have considered the use of an
> > IOC with Stream
> > > Device, to produce PV's which would communicate directly to
> > one of the
> > > RPC servers over the network.
> > >
> > > This would be a round-about way to use EPICS for RPC's
> > >
> >
> >
> >
>
>
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- References:
- EPICS for implementation of Remote Procedure call Mahajan Kirti
- Re: EPICS for implementation of Remote Procedure call Andrew Johnson
- Re: EPICS for implementation of Remote Procedure call S. Banerian
- Remote IOC reboot Was(EPICS for implementation of Remote Procedure call) Emmanuel Mayssat
- RE: Remote IOC reboot Was(EPICS for implementation of Remote Procedurecall) Allison, Stephanie
- Navigate by Date:
- Prev:
Re: Remote IOC reboot [was: EPICS for implementation of Remote Procedure Call] Ralph Lange
- Next:
RE: Remote IOC reboot [was: EPICS for implementation of RemoteProcedure Call] Dalesio, Leo
- 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: Remote IOC reboot [was: EPICS for implementation of Remote Procedure Call] Maren Purves
- Next:
Re: EPICS for implementation of Remote Procedure call Elliott Wolin
- 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
|