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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: procServ softIOC server - V2.5.0 released |
From: | Ralph Lange <[email protected]> |
To: | [email protected] |
Cc: | EPICS Tech Talk <[email protected]> |
Date: | Thu, 03 Dec 2009 09:41:46 -0500 |
On Wed 02 Dec 2009 18:35:47 S. Banerian wrote:
Davidsaver, Michael wrote:I start softIocs with a system init script at boot. We use debian, but it shouldn't be hard to adapt it to other *nix systems. http://pubweb.bnl.gov/~mdavidsaver/files/sysv-rc-softioc-1.1.tar.gzWe also use a sysv init script to start up procserv on boot, and for stopping/restarting, and we use an xml/rpc service for remote start/stop/restart of procserv via the init script.
BESSY also uses a sysv script.The xml/rpc service sounds like a very nice add-on I'd definitely be interested in. Is it available?
I was thinking about a Nagios check that connects to the public log port and analyzes procServ's connection message to see if the child is up. Should be pretty straightforward. Never managed to actually start working on it, though.
Hm ... maybe I should add a "contrib" section to the project to collect all this stuff.
Ralph