Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 80558 - After installing SpamAssassin 3.0.2 and starting it with "/etc/init.d/spamd" - spamd fails
Summary: After installing SpamAssassin 3.0.2 and starting it with "/etc/init.d/spamd" ...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: High minor
Assignee: Gentoo Perl team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-03 02:58 UTC by Thorsten Edler
Modified: 2005-02-07 11:17 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Edler 2005-02-03 02:58:56 UTC
Problem: After installing SpamAssassin 3.0.2 to the system and using the runlevel-file in /etc/init.d/ for starting spamd, the spamd-program fails with "Can't find/stat spamd: No such file or directory"

Solution: In the file /etc/init.d/spamd, which comes with a new installation of SpamAssassin has a wrong path-setting for the spamd-executable.

Wrong (old): /usr/bin/spamd
Right (new): /usr/sbin/spamd

You just have to change the path for spamd and all will be fine with that in future installations. :o)

Reproducible: Always
Steps to Reproduce:
1. Installing SpamAssassin 3.0.2
2. Copying the file /etc/init.d/cfg00XYZ_spamd, which comes with a new installation to /etc/init.d/spamd (overwriting)
3. Starting spamd with /etc/init.d/spamd start

Actual Results:  
There's an error like this one
"Can't find/stat spamd: No such file or directory"
 

Expected Results:  
Starting the spamd-program at the first time after an installation... would be
nice. :o)

No emerge-info necessary, because it's easy to solve "the problem". Just change
the executable-path for spamd in the standard /etc/init.d/spamd file of the
gentoo-install of SpamAssassin to /usr/sbin/spamd.
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2005-02-03 03:55:00 UTC
All fine here with spamassassin-3.0.2-r1. Looks like a local problem.
Comment 2 David 2005-02-03 14:09:55 UTC
Looks fine for me too on two machines running SpamAssassin 3.0.2-r1.
Comment 3 Michael Cummings (RETIRED) gentoo-dev 2005-02-07 11:17:46 UTC
Afraid I'm going to have to agree that this is invalid. The 3.0.0-spamd.init file in mail-filter/spamassassin/files/ points to sbin, and I know I haven't made any changes to the init file since importing it, and the only thing cvs log says is a header change. Going to have to chalk this up to a fluke.