Re: [tcljava-dev] Behaviour of exec in jacl. out.

[Patrick F. <fin...@gm...>]

2009/5/3 Patrick Finnegan <fin...@gm...>:
> Running JACL 1.4.2 under AIX 5.3.
>
> How does exec under JACL handle stdout.  Seems to be different to Tcl.
>  I would imagine the differences are java related i.e. jacl runs
> inside java which has it's own process  running under the OS where as
> the Tcl process runs inside the OS with no Java layer in between.
> Maybe Jython has the same issues.
>
> The main thing here is that redirect to a file(> EM_run_proxy.log)
> does not work under JACL
> .
> 1.  No process id returned.
>
> JACL
> ******
> wsadmin>exec nohup EM_run_proxy.sh -catName CreateSuspects  &
> pid0
>
> TCLSH
> ********
>
> %exec nohup EM_run_proxy.sh -catName CreateSuspects  &
> 876612
> % Sending nohup output to nohup.out.
>
> 2.  No redirect to output file.
>
> JACL
> *******
>
> wsadmin>exec nohup EM_run_proxy.sh -catName CreateSuspects > EM_run_proxy.log
>
> No file gets created.
>
> TCLSH
> ********
>
> % exec nohup EM_run_proxy.sh -catName CreateSuspects > EM_run_proxy.log &
> 876614
>
> EM_run_proxy.log is created and contains stand out.
>

There is definitely a difference in behaviour.

JACL does not create myfile.txt.
wsadmin>exec echo "test data" > myfile.txt
test data > myfile.txt

Tcl creates myfile2.txt

% exec echo "test data" > myfile2.txt
%