Re: just too late telling me job terminated

[Ralph Corderoy]

Hi Paul,

> > > <<Ctrl-Z>>
> > > [1]+  Stopped                 sh y
> > > $ kill %
> > > <<PS: why the blank line before these jobs messages?>>
> > > [1]+  Stopped                 sh y
> > > $ mail chet
> ..
> > > [1]+  Terminated              sh y
> >
> > I think bash is telling you what your OS is telling it.  Try `kill
> > -9 %' instead.
>
> I don't think that will make a difference.  The job apparently did die
> as a result of SIGTERM.  SIGKILL won't make it die any faster.

My thinking was SIGTERM can be caught by the shell, it can tidy up, then
quit.  bash might see some of that before the exit.  SIGKILL can't be
caught so bash gets to see the child process has quit all the sooner.

Could be wrong, but that was the reasoning.

Cheers,


Ralph.