Re: Running softIoc's in the background

["Paul Sichta" <psichta@pppl.gov>]

Malcom,
I use an indirect method to call st.cmd. I can't recall why I ended up 
doing it that way. As Eric suggested I have specified the path for the 
executable. Does the envPaths file look correct?

$ cat st.boot_iocs1
#!/bin/csh
cd /eprun/ioc157/iocBoot/ioclin7
screen -d -m -S ioc -h 1000 ./iocstart

$ cat iocstart
#!/bin/csh
../../bin/linux-x86/lin7 st.cmd


-ps


----- Original Message ----- 
From: "Eric Norum" <norume@aps.anl.gov>
To: "Walters, M (Malcolm)" <M.Walters@diamond.ac.uk>
Cc: <tech-talk@aps.anl.gov>
Sent: Tuesday, November 08, 2005 12:23 PM
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 <norume@aps.anl.gov>
> Advanced Photon Source
> Argonne National Laboratory
> (630) 252-4793