Re: signal handling on OpenBSD and NetBSD

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Ralf Wildenhues on 1/11/2009 5:45 AM:
> 
> 
> With this applied, the testsuite completes on both systems.  A parallel
> testsuite run is still not stoppable with C^Z (non-parallel seems to
> work), but it is interruptible with C^C.  Of course, now it generates
> additional slightly ugly output:

I tend to think that ugly, but functional, output outweighs pretty output
with the potential to hang.  If you feel comfortable applying the patch to
omit 'set +m' unless we can come up with something better, then go ahead
and apply it.
> 
> So the question is now how to go on.  As a lowest common denominator, we
> could just not use 'set +m' anywhere, and live with the additional noise
> on stderr.  Testing per system/shell used seems awkward and not trivial
> from within Autotest.  But at least that should allow 2.64 to be
> released.

Would an 'exec 2>/dev/null' in place of 'set +m' be useful, since we've
already announced on stderr that the testsuite was interrupted, or does
that have the potential of masking other fallout?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklsllIACgkQ84KuGfSFAYCZsACfZ40EL4pANBUqp0XmbBeVCAo8
IZMAoIOxSCJJf+VoVlBXRWEP/Pvo5qFA
=QnNO
-----END PGP SIGNATURE-----