Very Computer

Do you know about this issue ?

Why not a sample {exit 1; } ?

Thanks you !

Quote:> Do you know about this issue ?

> Why not a sample {exit 1; } ?

[...]

That's to set $?, for a trap on EXIT (0) to get it.

--
Stphane

So why do we need an extra { exit 1 } for that ? EXIT (0) gets called
just before the termination of the shell script.

[/tmp]$ cat trap.sh
#! /bin/sh

touch "/tmp/test.trap"
ls -l "/tmp/test.trap"

trap 'rm -rf /tmp/test.trap;' 0

{ exit 1 ; }

[/tmp]$ ls -l /tmp/trap.test
ls: /tmp/trap.test: No such file or directory
[/tmp]$ ./trap.sh
-rw-r--r--    1 xxxxxxxx g900            0 Feb 28 04:06 /tmp/test.trap
[/tmp]$ echo $?
1
[/tmp]$ ls -l /tmp/trap.test
ls: /tmp/trap.test: No such file or directory
[/tmp]$

The same is the case if I introduce,
        { (exit 1); exit 1;}

[/tmp]$ cat trap.sh
#! /bin/sh

touch "/tmp/test.trap"
ls -l "/tmp/test.trap"

trap 'rm -rf /tmp/test.trap;' 0

{ (exit 1); exit 1; }

[/tmp]$ !vi
vi trap.sh
[/tmp]$ ./trap.sh
-rw-r--r--    1 xxxxxxxx g900            0 Feb 28 04:09 /tmp/test.trap
[/tmp]$ echo $?
1
[/tmp]$

If the above illustration is not right, could you let me know how
exactly the OP works ?

Thanks.
Vino

[...]

Compare this:

sh -c '
  trap "
    ret=\$?
    echo in exit trap
    exit \"\$ret\"
  " EXIT
  exit 1
'; echo $?

with:

sh -c '
  trap "
    ret=\$?
    echo in exit trap
    exit \"\$ret\"
  " EXIT
  (exit 1); exit 1
'; echo $?

In the first case, the return status of the script will be "0"
(success) even though we called "exit 1" (which meant we want to
report an error).

Quote:> [/tmp]$ cat trap.sh
> #! /bin/sh

> touch "/tmp/test.trap"
> ls -l "/tmp/test.trap"

> trap 'rm -rf /tmp/test.trap;' 0

> { exit 1 ; }

> [/tmp]$ ls -l /tmp/trap.test
> ls: /tmp/trap.test: No such file or directory
> [/tmp]$ ./trap.sh
> -rw-r--r--    1 xxxxxxxx g900            0 Feb 28 04:06 /tmp/test.trap
> [/tmp]$ echo $?
> 1
> [/tmp]$ ls -l /tmp/trap.test
> ls: /tmp/trap.test: No such file or directory
> [/tmp]$

> The same is the case if I introduce,
>    { (exit 1); exit 1;}

[...]

See info -f autoconf --index-search=exit

The point is you may get rm's exit status in some shells if
it's not null.

--
Stephane

It's sort of a "workaround".

In some shells, this exit status is still "pending"
and not visible in the handler yet; there you see
the next recent status instead.

It's for example pending in Bourne, ksh88, zsh.
It's already available in ksh93, bash, ash, pdksh