From: shags72 on
I am wanting to use the open in the same manner as this script that
uses exec. Is there any way to pull this off?

exec notepad.exe $mom_external_filename

Reason being that my embedded tcl has an issue with exec but
supposedly not open. I just can't figure out the pipeline thing that
goes along with this.
From: Bruce on
shags72 wrote:
> I am wanting to use the open in the same manner as this script that
> uses exec. Is there any way to pull this off?
>
> exec notepad.exe $mom_external_filename
>
> Reason being that my embedded tcl has an issue with exec but
> supposedly not open. I just can't figure out the pipeline thing that
> goes along with this.

syntax -wise it would just be

open "| notepad.exe $mom_external_filename"

but I would be surprised if the system can't use exec but can use
open with a pipeline. (maybe the "open is fine" is based on just opening
files).

Good luck,
Bruce
From: Christian Rapp on
On Jun 12, 5:39 am, shags72 <je...(a)mtco.com> wrote:
> I am wanting to use the open in the same manner as this script that
> uses exec. Is there any way to pull this off?
>
>    exec notepad.exe $mom_external_filename
>
> Reason being that my embedded tcl has an issue with exec but
> supposedly not open. I just can't figure out the pipeline thing that
> goes along with this.

Maybe you could describe what does not work with your exec so we could
try to solve this.

Regards
From: shags72 on
On Jun 12, 3:22 am, Christian Rapp <rapp....(a)googlemail.com> wrote:
> On Jun 12, 5:39 am, shags72 <je...(a)mtco.com> wrote:
>
> > I am wanting to use the open in the same manner as this script that
> > uses exec. Is there any way to pull this off?
>
> >    exec notepad.exe $mom_external_filename
>
> > Reason being that my embedded tcl has an issue with exec but
> > supposedly not open. I just can't figure out the pipeline thing that
> > goes along with this.
>
> Maybe you could describe what does not work with your exec so we could
> try to solve this.
>
> Regards

Ok the syntax problem was I wasn't using the quotes as I thought that
this was the syntax just didn't realize the spaces would cause
problem. Thanks.

As far as the problem with exec goes I am not sure I can explain it as
I don't have access to the base code to the program. What happens is
if using exec to open something it inconsistently hangs the program
and you must kill your session. Although if you set the affinity of
the program process to a single cpu then it won't hang. This is what I
had been doing but now the program is capable of using multi cpus and
we wouldn't be able to take advantage of the time savings. Which
people have tested and reported huge time savings, so I have to fix
this. Hope I explained this well enough and that this makes sense to
you. Thanks.
From: Alexandre Ferrieux on
On 12 juin, 15:29, shags72 <je...(a)mtco.com> wrote:
>
> What happens is
> if using exec to open something it inconsistently hangs the program
> and you must kill your session. Although if you set the affinity of
> the program process to a single cpu then it won't hang. This is what I
> had been doing but now the program is capable of using multi cpus and
> we wouldn't be able to take advantage of the time savings. Which
> people have tested and reported huge time savings, so I have to fix
> this. Hope I explained this well enough and that this makes sense to
> you. Thanks.

When you say "set the cpu affinity of the process", are you talking
about the (embedded Tcl) parent, or about the (other program) child ?
If you haven't already, please try both configurations and report
which one hangs.

-Alex