On Mon, 2004-03-22 at 17:03, Anders Norrbring wrote: > Alright Alex! Thanks! Now I get this in the spamassassin lint run: > > debug: DCCifd is available: /var/dcc/dccifd > debug: dcc_home not defined, should not get here > > Not that I know what it means by the 2:nd line, dcc_home shouldn't be > explicitly defined as of what I can make out of the docs. Anyway, IF I set > dcc_home /var/dcc in my local.cf file, then I get errors; >
Well, I have dcc_home defined and it works. Here is the full list that I have and of course the path will need to be changed. use_dcc 1 dcc_path /opt/csw/dcc/ dcc_home /opt/csw/dcc/ dcc_dccifd_path /opt/csw/dcc/dccifd > debug: leaving helper-app run mode > DCCifd -> check skipped: Connection refused connect: Connection refused > ...propagated at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Dns.pm > line 617. > This is probably a permission issue with the user running the dcc process. I use a user and group of dcc and the dccifd process has dcc listed as the owner. Also, user dcc owns the home directory and most everything in the directory, except libexec and cgi-bin. > > So I let it be undefined, seems like it should work by now.. By the way, > how do I *stop* dccifd? I can start it simple enough by the start-dccifd > script, but not stop it? But it should feel "cleaner" to shut it off when > system is going down for halt or reboot. What you should use is <dcc_home>/libexec/rcDCC. I copied that file to /etc/init.d/ and made symlinks in rc2.d. As long as dcc_conf is setup properly, the script should work as is. Alex
