Where does "Terminated" message comes from?

[Michael Wang]

(1)

Here is the test program:

--
$ cat trap6.ksh
#!/bin/ksh
trap 'print a; print b' exit
sleep 10

exit 3
--

when killed, it produces message:

a
b
Terminated

on screen. "Terminated" output is neither stdout nor stderr, where
does it come from, and how to capture it?

(2)

However, if run by another shell:

--
$ cat 1.ksh
exec 1>1.1a 2>1.1b
../trap6.ksh
--

The "Terminated" output is changed slightly, and it is in run_trap6
stderr:

1.ksh[2]: 16817 Terminated

Why?
--
Michael Wang * [url]http://www.unixlabplus.com/[/url] * [email]mwang@unixlabplus.com[/email]

[Michael Wang]

(1)

Here is the test program:

--
$ cat trap6.ksh
#!/bin/ksh
trap 'print a; print b' exit
sleep 10

exit 3
--

when killed, it produces message:

a
b
Terminated

on screen. "Terminated" output is neither stdout nor stderr, where
does it come from, and how to capture it?

(2)

However, if run by another shell:

--
$ cat 1.ksh
exec 1>1.1a 2>1.1b
../trap6.ksh
--

The "Terminated" output is changed slightly, and it is in run_trap6
stderr:

1.ksh[2]: 16817 Terminated

Why?
--
Michael Wang * [url]http://www.unixlabplus.com/[/url] * [email]mwang@unixlabplus.com[/email]

[Darren Dunham]

Michael Wang <mwang@unixlabplus.com> wrote:

> (1)

> Here is the test program:

> --
> $ cat trap6.ksh
> #!/bin/ksh
> trap 'print a; print b' exit
> sleep 10

> exit 3
> --

> when killed, it produces message:

> a
> b
> Terminated

> on screen. "Terminated" output is neither stdout nor stderr, where
> does it come from, and how to capture it?

"It" (meaning the script) does not produce that message. Instead, your
shell which launched the script produced the message. You can see the
same thing with a script that only does a 'sleep 10'.

> (2)

> However, if run by another shell:

> --
> $ cat 1.ksh
> exec 1>1.1a 2>1.1b
> ./trap6.ksh
> --

> The "Terminated" output is changed slightly, and it is in run_trap6
> stderr:

> 1.ksh[2]: 16817 Terminated

> Why?

Because this time you didn't run trap6 from your interactive shell.
This time your subshell (which is 1.ksh) ran the script. The parent
script is responsible for the message, and it sends it on stderr.

--
Darren Dunham [email]ddunham@taos.com[/email]
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

[John DuBois]

In article <dcUUa.14$Uc3.36694@news.uswest.net>,
Michael Wang <mwang@unixlabplus.com> wrote:

>(1)
>
>Here is the test program:
>
>--
>$ cat trap6.ksh
>#!/bin/ksh
>trap 'print a; print b' exit
>sleep 10
>
>exit 3
>--
>
>when killed, it produces message:
>
>a
>b
>Terminated
>
>on screen. "Terminated" output is neither stdout nor stderr, where
>does it come from, and how to capture it?

It comes from the shell you ran your test program from. The shell notices that
the test program was killed by SIGTERM, so it prints "Terminated". If you want
to know whether this occured, you can check the exit status as recorded in $?.
If you want to avoid the "Terminated" message, run it in a subshell:

( testprog ) 2>/dev/null

John
--
John DuBois [email]spcecdt@armory.com[/email] KC6QKZ/AE [url]http://www.armory.com/~spcecdt/[/url]