spamc/spamd does not use UNIX sockets. We experimented briefly with a patch to CVS a few days ago which had UNIX sockets enabled as an option, but there were problem so it's backed out for now and won't be in 2.2 -- since there is a "nscd" in the socket name, I expect that your upgrade changed your /etc/resolv.conf or somehow altered the way name resolution on you machine works. Try "host localhost" on the command line and see what happens. nscd by the way is the caching nameserver that RH uses I think. Sounds to me like a hostname resolution problem.
C Dan Wilson wrote: DW> Date: Fri, 12 Apr 2002 12:16:10 -0600 DW> From: Dan Wilson <[EMAIL PROTECTED]> DW> To: Theo Van Dinter <[EMAIL PROTECTED]> DW> Cc: [EMAIL PROTECTED], DW> Marcellus Barrus <[EMAIL PROTECTED]> DW> Subject: Re: [SAtalk] spamc not working also DW> DW> I've actually run an strace on it and determined that I am missing a socket DW> file. DW> DW> /var/run/.nscd_socket is not found. I'm not sure what creates that though. DW> Any suggestions would help. Another user mentioned that I should have DW> a /var/run/spamass.sock= file, that I could just symlink, but that doesn't DW> exist either. DW> DW> -Dan DW> DW> Quoting Theo Van Dinter <[EMAIL PROTECTED]>: DW> DW> > On Fri, Apr 12, 2002 at 09:02:18AM -0600, Dan Wilson wrote: DW> > > SpamAssassin 2.11 DW> > > RH 7.2 Linux 2.4.7-10 DW> > > glibc 2.2.4 (someone mentioned this might be the problem) DW> > > Qmail (although I haven't gotten to the qmail-scanner integration yet) DW> > > I have downloaded the other packages (razor, qmail-scanner, etc) but I DW> > can't DW> > > get the first step to work. So there is no point in continuing DW> > DW> > Well, it's not glibc in and of itself. I've had SA running on a similar DW> > setup for quite a while now. DW> > DW> > How did you install the stuff? I used the SRPM, compiled up the RPM DW> > and installed it. DW> > DW> > > I've got spamd working... (at least I think so). When I stop spamd and try DW> > to DW> > > run something through spamc (spamc -c < sample-spam.txt), I get a 0/0 DW> > > printed. If spamd is running, it doesn't print anything. I also removed DW> > the - DW> > > c and the resulting email doesn't have any new header tags. DW> > DW> > Hmmm. It sounds like spamc can't talk to spamd. just to check -- is DW> > spamd running on port 783, and spamc trying to connect to 783 as well? DW> > I seem to remember having a problem once where spamd had a port specified DW> > to it via the rc script, and spamc just kept trying the default. Don't DW> > remember if that was an upgrade issue or a sysadmin-is-tired error. ;) DW> > DW> > -- DW> > Randomly Generated Tagline: DW> > "The quickest way to double your money is to fold it in half and put it DW> > back in your pocket." - Zen Musings DW> > DW> DW> DW> DW> DW> _______________________________________________ DW> Spamassassin-talk mailing list DW> [EMAIL PROTECTED] DW> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk DW> DW> DW> _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
