[Bug 3817] New: spamd failed to restart on receiving SIGHUP (kill -HUP _pid_)

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3817

           Summary: spamd failed to restart on receiving SIGHUP (kill -HUP
                    _pid_)
           Product: Spamassassin
           Version: 3.0.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: sa3.z.chau@xoxy.net


Dear developers,

I just upgraded my SA 2.63 to SA 3.00 GA and found that spamd had problems
restarting on receiving HUP signal from kill.  It simply got killed.

A log for your reference:
$ sudo ps ax | grep spam
 2453 ?        S      0:01 /usr/bin/spamd -d -m5 -u mail                    
 2458 ?        S      0:00 spamd child                                      
 2459 ?        S      0:00 spamd child                                      
 2460 ?        S      0:00 spamd child                                      
 2461 ?        S      0:00 spamd child                                      
 2462 ?        S      0:00 spamd child                                      
$ sudo kill -HUP 2453
$ sudo tail /var/log/maillog
Sep 24 12:49:38 mail spamd[2453]: server successfully spawned child process, pid
2460 
Sep 24 12:49:38 mail spamd[2453]: server successfully spawned child process, pid
2461 
Sep 24 12:49:38 mail spamd[2453]: server successfully spawned child process, pid
2462 
Sep 24 12:50:03 mail spamd[2453]: server hit by SIGHUP, restarting 
Sep 24 12:50:03 mail spamd[2453]: child 2458 killed successfully 
Sep 24 12:50:03 mail spamd[2453]: child 2461 killed successfully 
Sep 24 12:50:03 mail spamd[2453]: child 2459 killed successfully 
Sep 24 12:50:03 mail spamd[2453]: child 2462 killed successfully 
Sep 24 12:50:03 mail spamd[2453]: child 2460 killed successfully 
$ sudo ps ax | grep spam
$
(nothing)

other info: redhat 8, perl 5.8.0

Thanks,
Sam



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.