Joerg Schilling wrote:
Rainer Orth <[EMAIL PROTECTED]> wrote:

* At one time, I had to abort nightly with ^C.  Unfortunately, the
  sub-dmakes ignored this an ran along happily.  It took me some effort to
  kill off the whole bunch ;-(
This is interesting. Are you using bash at some important place here?
Indeed: nightly is started from bash.

Then you may like to check whether your problem is caused by a well known bash bug:

bash does job control for "sh -c command" which results in different process groups of sub-commands (e.g. in case that /bin/sh is bash and you use layered make systems).

Nightly's children don't die when it exits because of the task. Using resource containers like tasks changes the contract behavior.

Nightly should probably just kill its entire task when it traps a SIGINT.

And while we're at it, nightly should probably ignore SIGHUP too.

- Eric
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to