On 28.11.2016 17:05, Benoit RAT wrote:
> - 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.
We use procServ (as Mark mentioned) and also use conserver for (possibly
remote) console access to all IOCs (soft IOCs on Linux and VME based
IOCS with RTEMS). Users just say "console <ioc name>" and immediately
get console access from (almost) everywhere... perhaps not the safest
method but quite simple to configure.
Cheers
Ben
--
"Make it so they have to reboot after every typo." ― Scott Adams
Attachment:
signature.asc
Description: OpenPGP digital signature
- References:
- Asyn daemon + console + log Benoit RAT
- Navigate by Date:
- Prev:
Re: Asyn daemon + console + log Benoit Rat
- 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
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Asyn daemon + console + log Keith Thorne
- Next:
SNL sequencer apparently losing connection to underlying network Kevin Meyer
- 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
|