|Summary:||spamd options - order seems to be important|
|Product:||Spamassassin||Reporter:||Paul McIlfatrick <paul.mcilfatrick>|
|Component:||spamc/spamd||Assignee:||SpamAssassin Developer Mailing List <dev>|
Description Paul McIlfatrick 2006-10-19 04:42:31 UTC
Tried to get spamd to create a pid file. The following order of options did NOT work: /usr/perl5/bin/spamd -u mail -d -r /etc/exim/spamd.pid --syslog-socket=inet & Experimented and found that the following worked: /usr/perl5/bin/spamd -u mail -r /etc/exim/spamd.pid -d --syslog-socket=inet & Surely the order of options should not matter?
Comment 1 Theo Van Dinter 2006-12-05 12:24:37 UTC
Hrm. The order shouldn't matter for options. SA just calls Getopt::Long::GetOptions() to deal with the commandline though, so I don't think there's anything from a SA perspective here if there's misparsing going on. If this is still occurring, I'd try upgrading the Getopt::Long module, and then if that didn't change anything, go debugging in spamd to see if the module is parsing correctly.