Re: Asyn daemon + console + log

[Keith Thorne <kthorne@ligo-la.caltech.edu>]

At LIGO Livingston, we have also used the ‘tmux’ system for doing the same thing
At LIGO Hanford, I believe they are using procServ for some

Yes, I know, yet more ways to do it

	Keith Thorne

> On Nov 28, 2016, at 11:11 AM, Benoit Rat <benoit.rat.lists@gmail.com> wrote:
> 
> Thanks a lot!
> 
> I didn't though about screen but it meet perfectly my needs!
> Could you send me the start() command just to check how you do it?
> 
> Cheers,
> 
> 
> 
> 
> --
>  
> 
> Benoit RAT LAMY
> www.sevensols.com 
> 
> On Mon, Nov 28, 2016 at 5:53 PM, Rod Nussbaumer <bomr@triumf.ca> wrote:
> 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:* tech-talk-bounces@aps.anl.gov
> [mailto:tech-talk-bounces@aps.anl.gov] *On Behalf Of *Benoit RAT
> *Sent:* Monday, November 28, 2016 10:06 AM
> *To:* tech-talk@aps.anl.gov 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: benoit@sevensols.com <mailto:benoit@sevensols.com>
> 
> *www.sevensols.com <http://www.sevensols.com/> *
> 
> 
> 



------
Keith Thorne <kthorne@ligo-la.caltech.edu>
CDS Software Engineer
LIGO Livingston Laboratory
Livingston, LA 70754
Phone: (225)686-3168 Fax: (225)686-7189