>Number:         5504
>Category:       kern
>Synopsis:       signal handler doesn't get called again after execve)?
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          support
>Submitter-Id:   net
>Arrival-Date:   Wed May 27 23:20:01 1998
>Last-Modified:
>Originator:     TheMan
>Organization:
none
>Release:        1.2
>Environment:
System: NetBSD noc 1.2 NetBSD 1.2 (null) #4: Fri Oct 24 01:27:28 EDT 1997 root@noc:/usr/src/sys/arch/i386/compile/null i386

>Description:
	i have a program that catches SIGHUP and re-execs itself when it
	receives one.  unfortunately, the new process doesn't behave the
	same way.  is this "normal" signal behavior?
>How-To-Repeat:
	write a program that re-execs itself after receiving a SIGHUP.
	send it a SIGHUP.  then send the new process a SIGHUP.  notice
	that it doesn't work.
>Fix:
	i looked at sendmail code (since it does this correctly) and
	noticed that it mucks about with sigprocmask(2).  shouldn't
	an exec clear such things?
>Audit-Trail:
>Unformatted: