https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8384
--- Comment #6 from Dan Mahoney <[email protected]> --- Okay, thinking about this, the argument for LEAVING the procname unchanged is "because people want to see the arguments in ps so that they can restart it" Here's an example of what I see in ps under FreeBSD 14.3: /usr/local/bin/perl -T -w /usr/local/bin/spamd -D -u spamd -m 53 -x --virtual-config-dir=/usr/local/etc/mail/spamassassin/users/dayjob.org/%u -l -i ssl:*:784 -i *:783 -A 10.0.0.0/24 -d -r /var/run/spamd/spamd.pid ...except that wasn't how I started spamd anyway. I (or the startup script) never typed "perl", I typed "spamd". I mean, the problem is, we do *two* things when we rename. 1) change the name from "perl" to "spamd" (all processes started via a shebang line inherit the name of the interpreter, even if, in ps, they retain all the arguments). 2) When we do the name change, we squash the arguments, too. (I'm given to understand BSD and Linux do this a bit differently from each other). Could this just be fixed to: if (would_log("dbg")) { $0 = "spamd @ORIG_ARGV"; # full cmdline visible in ps aux } else { $0 = 'spamd'; # bug 8036 } ...alternatively, I'm reaching out to the pkg maintainer, to see if he can have the startup script look for a process named "perl" instead of "spamd" when it detects that you've got -D in the spamd_flags set. ...alternatively ALTERNATIVELY, we can just maintain that alternate setup script in house, but this has bothered me for literally decades. -- You are receiving this mail because: You are the assignee for the bug.
