EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  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  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Asyn daemon + console + log
From: Rod Nussbaumer <[email protected]>
To: [email protected]
Date: Mon, 28 Nov 2016 08:53:39 -0800
We run IOCs in Gnu screen sessions, accomplishing all three of your requirements. The screen sessions are started in multi-user mode, through some scripting in the init system. This is accomplished on headless systems by exploiting the 'stuff' command of the screen applicaton to stuff commandlines into the screen session to launch the IOC application(s). Logging is done by screen, and log rotation using conventional logrotate tools.

Users use ssh to connect to the IOC host, and then connect to the screen session. This part is augmented with a GUI tool which runs on a common server host that lets users browse lists of IOCs and connect to sessions by clicking on menu items.

Rod Nussbaumer
TRIUMF,
Vancouver, Canada


On 11/28/2016 08:40 AM, Mark Rivers wrote:
We use procServ to handle tasks 1 and 3, and logrotate for task 2.  A
simple etc/init.d script can be used to start the procServ/IOC.

https://sourceforge.net/projects/procserv/

Mark

*From:* [email protected]
[mailto:[email protected]] *On Behalf Of *Benoit RAT
*Sent:* Monday, November 28, 2016 10:06 AM
*To:* [email protected] list
*Subject:* Asyn daemon + console + log

Hi guys,

I was wondering if someone could help me implement the following:

    * Already done: I need to start my Asyn IOC as a daemon so that it
      is executed at startup (A simple /etc/init.d/ scripts is doing the
      job)
    * Already done: I need to store all the outputs of my IOC into a
      file (into /var/log/asyn/xxxxx.log with a logrotate to avoid
      getting a problem with size)
    * I want the user able to connect to the epics-ioc console (Maybe
      through /dev/ttySxx)

I have manage to get the two first thing working but I can not get the
combination of the three. Someone has an idea, is it possible to access
to the console?

Maybe running the IOC as a daemon is not the best solution, but I would
really like to have my IOC started when I power on my rack.


--

Image removed by sender. <http://www.sevensols.com/>

*Benoit RAT LAMY*

fix. *(+34) 958 285 024*

e-mail: [email protected] <mailto:[email protected]>

*www.sevensols.com <http://www.sevensols.com/> *



Replies:
Re: Asyn daemon + console + log Benoit Rat
References:
Asyn daemon + console + log Benoit RAT
RE: Asyn daemon + console + log Mark Rivers

Navigate by Date:
Prev: Channel Archiver - Data Conversion / Export from File to RDBArchiver PostgreSQL database Zumbruch, Peter Dr.
Next: Re: EPICS/RTEMS Compilation errors Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Asyn daemon + console + log Mark Rivers
Next: Re: Asyn daemon + console + log Benoit Rat
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 28 Nov 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·