Groups | Search | Server Info | Login | Register

Groups > comp.lang.tcl > #55547

Re: exec not exec'ing

Show all headers | View raw

On 3/6/2026 2:40 PM, Rich wrote:
> 
> Then you may need to make use of 'auto_execok' to launch the tcl
> script.

I will have to try that!  I stumbled into a solution earlier which is 
the same as that suggested by meshparts.

I wonder if you have an insight into this though:

I have a socket in a script. I would like to pass it to a separate 
script I am exec'ing which will write to it and then close it when it is 
done.

I am using this syntax:

exec $script $arg1 $arg2  >@ $sock

This command sets up the script so that the socket is now its stdout. 
This works OK for files: If I open a file, and use the file handle 
instead of a socket in the above statement, everything works fine. The 
script's output ends up in the file.

But for sockets, it doesn't work for some reason.  It seems that the 
script is not able to write to the socket.

Perhaps this is not possible, I am not sure.

Back to comp.lang.tcl | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

exec not exec'ing saito <saitology9@gmail.com> - 2026-03-06 12:11 -0500
  Re: exec not exec'ing meshparts <alexandru.dadalau@meshparts.de> - 2026-03-06 18:26 +0100
    Re: exec not exec'ing saito <saitology9@gmail.com> - 2026-03-06 14:13 -0500
  Re: exec not exec'ing Rich <rich@example.invalid> - 2026-03-06 18:23 +0000
    Re: exec not exec'ing saito <saitology9@gmail.com> - 2026-03-06 14:12 -0500
      Re: exec not exec'ing Rich <rich@example.invalid> - 2026-03-06 19:40 +0000
        Re: exec not exec'ing saito <saitology9@gmail.com> - 2026-03-06 15:34 -0500
          Re: exec not exec'ing Rich <rich@example.invalid> - 2026-03-07 15:13 +0000
        Re: exec not exec'ing et99 <et99@rocketship1.me> - 2026-03-06 14:11 -0800

csiph-web