Which signal >(process) receives after main shell exits?

Which signal >(process) receives after main shell exits?

[Sebastian Gniazdowski]

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

Hello,

% fun() {
   setopt localtraps
   trap "echo waiting >> /tmp/reply; sleep 2; echo bye >> /tmp/reply; exit
1;" EXIT
   echo "My PID: $sysparams[pid]"
   repeat 1000; do
      read -r -t 1 line
   done
}

% exec {MYFD}> >(fun)
% exit

Above works – fun() will receive the trap, messages will appear in
/tmp/reply.

My question: can be "EXIT" replaced by some actual signal? I've tried PIPE,
HUP, INT, TERM and they didn't work.

-- 
Best regards,
Sebastian Gniazdowski

Re: Which signal >(process) receives after main shell exits?

[Sebastian Gniazdowski]

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

On 11 May 2018 at 07:18, Sebastian Gniazdowski <sgniazdowski@gmail.com>
wrote:

> Hello,
>    repeat 1000; do
>       read -r -t 1 line
>    done
>

There's a resolution – Zsh apparently doesn't manage >(process). No signal
is being sent. The function exits after main shell exits, because `read`
starts to ignore -t 1 timeout, after it somehow detects that stdin is
invalid. Thus quick 1000 iterations of the loop execute, and `fun` exits,
triggering EXIT trap.

I wonder if this is a discovery of other way of running disowned processes.

-- 
Best regards,
Sebastian Gniazdowski