On May 5, 2004, at 12:21 AM, Cole wrote:
Hey
Im writing a threaded program to handle connections coming from squid.
And
the program is working fine, except that i cant seem to set
signal(SIGPIPE,
SIG_IGN)
It doesnt give any errors when performing that command, and then when i
check to see what
Hey
Im writing a threaded program to handle connections coming from squid. And
the program is working fine, except that i cant seem to set signal(SIGPIPE,
SIG_IGN)
It doesnt give any errors when performing that command, and then when i
check to see what SIGPIPE is set to, it apparently isnt
-Matt
:- Hunk #1 from commit adds PS_NOCLDWAIT when SIG_IGN is used for
: SIGCHLD, so if I use
: sigemptyset(&sa.sa_mask);
: sa.sa_flags = 0;
: sa.sa_handler = SIG_IGN;
: sigaction(SIGCHLD, &sa, NULL);
: sigaction(SIGCHLD, NULL, &so);
: I get ad
Matt Dillon wrote:
> Umm. Terry, I really have no idea what you are talking about.
I am talking about being able to get the previous behaviour.
> What historical behavior? That FreeBSD was not properly
> dealing with SIG_IGN when every other UNIX does?
> So yo
:Matt Dillon wrote:
:> The issue here is first: since we are fixing a bug we might
:> as well be as compatible as possible with other platforms and,
:> second: on general principles it does make sense to keep SIG_IGN
:> operation independant from the newer SA_NOCLDWA
Matt Dillon wrote:
> The issue here is first: since we are fixing a bug we might
> as well be as compatible as possible with other platforms and,
> second: on general principles it does make sense to keep SIG_IGN
> operation independant from the newer SA_NOCLDWA
e here is first: since we are fixing a bug we might
as well be as compatible as possible with other platforms and,
second: on general principles it does make sense to keep SIG_IGN
operation independant from the newer SA_NOCLDWAIT stuff. A program
using SIG_IGN has absolutely no e
:- Hunk #1 from commit adds PS_NOCLDWAIT when SIG_IGN is used for
> : SIGCHLD, so if I use
> : sigemptyset(&sa.sa_mask);
> : sa.sa_flags = 0;
> : sa.sa_handler = SIG_IGN;
> : sigaction(SIGCHLD, &sa, NULL);
> : sigaction(SIGCHLD, NULL, &so);
&g
Cejka Rudolf wrote:
> Ok, I repeat it once again - in the full: If I use
>
> sigemptyset(&sa.sa_mask);
> sa.sa_flags = 0;
> sa.sa_handler = SIG_IGN;
> sigaction(SIGCHLD, &sa, NULL);
>
> zombies are still created in FreeBSD, which is against SUSv2.
You are corr
> I'll take a look at them tonight and (unless Dave wants to) I'll
> commit an update to -current and hold off the -stable MFC another
> few days.
I recieved some mail from Garrett on the standards side of the thing,
so I'll read and digest that.
I should be able to look after the -c
:- Hunk #1 from commit adds PS_NOCLDWAIT when SIG_IGN is used for
: SIGCHLD, so if I use
: sigemptyset(&sa.sa_mask);
: sa.sa_flags = 0;
: sa.sa_handler = SIG_IGN;
: sigaction(SIGCHLD, &sa, NULL);
: sigaction(SIGCHLD, NULL, &so);
: I get additional flag SA_NO
ll let Matt do the MFC when he feels ready.
Thanks for this commit, but it works exactly in the way, which
I wanted to avoid. It is something like "partially submitted and
not approved by me". Please, could you look once again on it?
Please please please... Thanks. ;-)
- Hunk #1 from com
On Sun, Jun 10, 2001 at 05:20:50PM -0700, Peter Wemm wrote:
> I agree totally. This should have been done ages ago, I've been burned on
> it a few times, but never badly enough to go fix it.
I've committed this - I'll let Matt do the MFC when he feels ready.
David.
To Unsubscribe: send
Matt Dillon wrote:
>
> :...
> :
> :sigemptyset(&sa.sa_mask);
> :sa.sa_flags = 0;
> :sa.sa_handler = SIG_IGN;
> :sigaction(SIGCHLD, &sa, NULL);
> :
> :z
:...
:
:sigemptyset(&sa.sa_mask);
:sa.sa_flags = 0;
:sa.sa_handler = SIG_IGN;
:sigaction(SIGCHLD, &sa, NULL);
:
:zombies are still created in FreeBSD, which is against SUSv2.
:
:My
Terry Lambert wrote (2001/06/08):
> > However, if I use "signal(SIGCHLD, SIG_IGN)", zombies are still
> > created in FreeBSD, which is against SUSv2.
I'm sorry that I used this shortening: I know that signal()
is implemented via sigaction() in FreeBSD's libc so I
Cejka Rudolf wrote:
>
> There is following paragraph in SUSv2:
>
> If a process sets the action for the SIGCHLD signal to SIG_IGN,
> the behaviour is unspecified, except as specified below. If the
> action for the SIGCHLD signal is set to SIG_IGN, child processes
Oops, kid's bugs. Thanks to David Malone ;-)
Cejka Rudolf wrote (2001/06/07):
> "if (ps->ps_sigact[_SIG_IDX(SIGCHLD)] = SIG_IGN)" is unnecessary.
^
==
> --- sys/kern/kern_sig.c.orig
There is following paragraph in SUSv2:
If a process sets the action for the SIGCHLD signal to SIG_IGN,
the behaviour is unspecified, except as specified below. If the
action for the SIGCHLD signal is set to SIG_IGN, child processes
of the calling processes will not be transformed into
19 matches
Mail list logo
