I see the same behaviour when I try it in this way. Using screen with a
script that calls the ioc startup script works, as suggested by several
people.
$ cat ./st.screen
#!/bin/sh
./st.boot
$ screen ./st.screen
Thank you for all of the help.
Malcolm
________________________________
From: Eric Norum [mailto:[email protected]]
Sent: 08 November 2005 17:23
To: Walters, M (Malcolm)
Cc: [email protected]
Subject: Re: Running softIoc's in the background
On Nov 8, 2005, at 11:12 AM, Walters, M (Malcolm) wrote:
I have been trying to run a Linux softIoc in the background by
using the
screen command. When I try to specify the startup script at the
same
time (i.e. "screen ./st.cmd"), the ioc starts but on any
caget/caput/...
command the screen terminates without any error message.
What happens if you specify the executable explicitly rather than
starting the executable from the script?
i.e.
screen /full/path/to/bin/linux-x86/iocExecutable st.cmd
If I start the screen and then run the startup script I don't
have any
problems. This problem occurs for every database we have tried.
Has
anybody else had any similar problems or any ideas what might be
causing
this?
We are running R3.14.7.
--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793
- Replies:
- Re: Running softIoc's in the background Kay-Uwe Kasemir
- Navigate by Date:
- Prev:
Re: Running softIoc's in the background john sinclair
- Next:
Re: Running softIoc's in the background Kay-Uwe Kasemir
- 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: Running softIoc's in the background john sinclair
- Next:
Re: Running softIoc's in the background Kay-Uwe Kasemir
- 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
|