The following reply was made to PR os-linux/2839; it has been noted by GNATS.
From: Roland Baer <[EMAIL PROTECTED]>
To: Marc Slemko <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: os-linux/2839: Noop-value for of Action->sa_flags passed to sigaction:
0x20000000
Date: Fri, 14 Aug 1998 15:46:18 +0200 (MEST)
Hello Marc,
On Wed, 12 Aug 1998, Marc Slemko wrote:
> On 12 Aug 1998, Roland Baer wrote:
>
> > >Environment:
> > Linux 2.0.33, libc5 Suse, Linux 5.2, Insure++4.1
> > >Description:
> > Problem is, that on Linux SA_INTERRUPT is defined, but according to
> > kernel sources, this is a noop.
>
> And exactly what problem does this cause? How does it show up?
SA_INTERRUPT is only defined for historical reasons, but nowadays also
used only internally.
Excerp from Linux Programming Guide (LPG):
* SA_INTERRUPT: Defined under Linux, but unused. Under SunOS, system
calls were automatically restarted, and this flag disabled that
behavior.
As sigaction never evaluates this flag, it makes no sense to set it.
Probably removing this flag on linux will prevent from problems with
future version of the kernel.
The question is not, why removing this flag, the question is, why
apache makes a system call with a noop flag. Maybe this is an
academic question.
I know, that I currently get the same binary, so you can change priority
to low.
>
Regards,
Roland
