https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7295
Bug ID: 7295
Summary: kill -HUP (still) changes ps name
Product: Spamassassin
Version: 3.4.1
Hardware: PC
OS: NetBSD
Status: NEW
Severity: normal
Priority: P2
Component: spamc/spamd
Assignee: [email protected]
Reporter: [email protected]
Created attachment 5377
--> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5377&action=edit
exec using perl_from_hashbang_line patch
After bug 5255 came bug 5419 where the problem was a name change in ps output
from "spamd" to "perl" after a SIGHUP.
In the same vein, I am seeing the change "perl" to "perl5.22.1" after a SIGHUP.
This is because when run, ps will show $perl_from_hashbang_line. After a SIGHUP
do_sighup_restart will change it to $^X (perl's built in $EXECUTABLE_NAME)
I think you might hope that the two would be the same, however, surprisingly on
my NetBSD system, perl and perl5.22.1 are hard linked, and $EXECUTABLE_NAME
returns perl5.22.1 when running a script with #!/usr/pkg/bin/perl - see
http://gnats.netbsd.org/50772.
Given this odd case, is there any advantage to using $^X rather than
$perl_from_hashbang_file? As you would hope they are the same, I assume not,
and the following patch uses perl_from_hashbang_file, and if it isn't found,
uses $^X.
Thoughts?
--
You are receiving this mail because:
You are the assignee for the bug.
