Running scilab scripts in the background (Linux)
Francis
I want to run a script which probably run for a 1/2 half day or so and
hence I want to run it in the background. I found on this forum the
commands to do it but the message was made in 1997. I tried to do this
>% scilab -nw < myscript.sce > myscript.sce.log &
but I get the following error message: "Scilab doesn't work if
standard input is not a terminal" and also the welcome words,
copyright stuff is printed on screen and not suppressed. As usual with
scilab documentation is difficult to find, but I am sure somebody
knows it on this forum.
Cheers,
Francis
Sylvestre Ledru
> Hi everybody,
>
> I want to run a script which probably run for a 1/2 half day or so and
> hence I want to run it in the background. I found on this forum the
> commands to do it but the message was made in 1997. I tried to do this
>
>>% scilab -nw < myscript.sce > myscript.sce.log &
Try
scilab -nw -f myscript.sce > myscript.sce.log &
I am currently working on something to simply this kind of things.
Btw, I recommand you subscribe to Scilab mailing list. You will get more
information about the dev, doc, etc
Sylvestre
Tim Wescott
If you're working in that area, I filed an enhancement request a while
ago for a mechanism to have Scilab exit with a non-zero exit status.
When I get to the phase in development where I'm generating big tables of
numbers at build time I like to have Scilab spit out a C file from within
my make file, but I'd like to be able to have my scripts be well behaved,
which means being able to indicate an error condition on exit so that
make can terminate.
Could you consider that as you compile your to-do list?
Thanks.
Sylvestre Ledru
Yep, I will try to add this feature for Scilab 5.2.
However, how do you see that in Scilab ?
By extending functions quit/exit with a input argument ? (like exit(-1) ?)
S
Francis
Hi, thanks for the tip
The command: "scilab -nw -f myscript.sce > myscript.sce.log &" seems
to work, although nothing is writing to the log file and the warnings
still appear on screen rather than in the file. Not perfect but it
gets the job done.
Francis
Tim Wescott
Allowing an argument to exit seems the most natural to me, then you would
call exit(0) for a normal termination, and exit(1), exit(2), etc., for
any abnormal terminations. (Note the positive numbers -- the linux shell
seems to expect a positive exit number to indicate an error condition,
and it certainly expects a zero to indicate truth, beauty and happiness.
The DOS/Windows console inherited this from unix, so it behaves the same).