-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 6/8/2009 2:59 PM:
If I understand this correctly, then there are one, or even two ways to
portably reset traps to their default value: either use reset only one
signal at a time:
trap 1; trap 2; trap 13; trap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 6/8/2009 2:59 PM:
If I understand this correctly, then there are one, or even two ways to
portably reset traps to their default value: either use reset only one
signal at a time:
trap 1; trap 2; trap 13; trap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Aaron Ucko on 6/6/2009 7:26 PM:
Aaron Ucko u...@ncbi.nlm.nih.gov writes:
necessary for #include limits.h to yield a definition of PATH_MAX.
Upon consideration, a better canary might be NAME_MAX or NGROUPS_MAX.
How is that? Are
Eric Blake e...@byu.net writes:
How is that? Are these more likely to be defined across all platforms
than PATH_MAX, showing that limits.h was valid?
Yes; in particular, the Hurd generally avoids hard limits of that sort,
but still has a genuine NAME_MAX, and additionally defines a nominal
