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  <20102011  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  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: copying output of Linux ioc to file
From: Ralph Lange <[email protected]>
To: EPICS Tech Talk <[email protected]>
Date: Fri, 23 Jul 2010 11:26:21 -0400
On 23.07.2010 10:29, Rod Nussbaumer wrote:
Till Straumann wrote:
There's also 'screen'

HTH
- T.

Yes.


Just to expand on that a little... Screen will allow multiple concurrent secure-shell connections to your IOC console, as well as logging all console activities to files. It assumes your console is accessible through a Linux host somehow, but this seems probable, from the description you gave initially. As far as I know, most Linux distributions either include Gnu screen as standard fare, or provide it as a package for use with the standard package manager. At TRIUMF, we use it heavily, and have a Perl/Tk application to aid in starting new sessions and selecting existing session for attachment.

Rod Nussbaumer
ISAC Controls, TRIUMF
Vancouver, Canada

In fact, screen was initially used as the standard way to start host-based soft IOCs in the background for later-on console access.


After reports on tech-talk in 2007 and 2008 [1] of screen hanging up IOCs (when users were using screen's rich features, such as browsing in the console history), procServ was used as an easier-to-use, a lot lighter and more appropriate replacement.

Especially in combination with a generic console logging and access package like conserver [2], soft IOC consoles get accessible and are logged in the very same way as terminal-server based VME IOCs, so that the command "console <myioc>" connects to to that IOC - soft or VME based. There are pages on the EPICS Wiki that describe such a setup in detail. [3]

conserver is part of all major distributions, procServ is part of Debian and derivatives, hopefully soon Fedora (waiting to be picked up by Fedora for >6 months now).

Cheers,
Ralph


[1] http://www.aps.anl.gov/epics/tech-talk/2007/msg01376.php
http://www.aps.anl.gov/epics/tech-talk/2008/msg00370.php
[2] http://www.conserver.com/
[3] http://www.aps.anl.gov/epics/wiki/index.php/How_to_Set_Up_a_Soft_IOC_Framework_on_Linux
(M. Davidsaver contributed a greatly improved version of the init script integration
http://www.aps.anl.gov/epics/wiki/index.php/How_to_Set_Up_Console_Access_and_Logging_for_VME_and_Soft_IOCs

References:
copying output of Linux ioc to file Patrick Thomas
Re: copying output of Linux ioc to file emmanuel_mayssat
Re: copying output of Linux ioc to file Till Straumann
Re: copying output of Linux ioc to file Rod Nussbaumer

Navigate by Date:
Prev: Re: Building host-based applications for cross-compiled targets Andrew Johnson
Next: RE: streamDev - ENUM Converter (%{string0|string1|...}) peter.owens
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: copying output of Linux ioc to file Rod Nussbaumer
Next: EDM: subclassing ProcessVariable to support custom DAQ Carl Schumann
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·