Not scientific, but I don't find much difference between using daemon and using the dccproc.
Since dccproc works 100% of the time, and the dccifd daemon can act quirky sometimes if you don't bring it and spamd up in the right order, I would use dccproc. My $.02 <<Dan>> | -----Original Message----- | From: Alex S Moore [mailto:[EMAIL PROTECTED] | Sent: Monday, March 22, 2004 4:55 PM | To: [EMAIL PROTECTED] | Subject: Re: dccifd | | On Mon, 2004-03-22 at 13:03, Stefan Ewert wrote: | | > i didnt work. i entered this in one line and got no error, but it | > still get this r/w socket not found error. | > but ps -A f shows the daemon running. | > | I made a post earlier about this. Add dcc_dccifd_path <fullpathname | to socket> to local.cf, along with possibly dcc_home and of | course 'use_dcc 1' | | > dont i have to start dccifd via start-dccifd? its strange, | because the | > pid file exists and spamassassin cant find it. | > | | Yes, there should be a process named dccifd. I use | <dcc_home>/libexec/rcDCC to start the process. Check that | dcc_conf has | only dccifd enabled. | | > btw. dccifd is in the given directory, so i think it is installed. | > | > if i want to activate dccifd, is it right to right to write | on instead off in | > dcc_conf and then reprocess this via cdcc "load map.txt" ? | | Yes, change dcc_conf, but cdcc has nothing to do with starting dccifd. | | Alex |
