Initially I was getting this error: unix dgram connect: Socket operation on non-socket at /usr/local/bin/spamd line 282 getservbyname failed for tcp at /usr/local/bin/spamd line 290 udp connect: nobody listening at /usr/local/bin/spamd line 290 failed to setlogsock(unix) on this platform; reporting logs to stderr
I did a search on google and found someone else's solution, which was to add --syslog-socket=inet option when starting spamd -----Original Message----- From: Matt Kettler [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 18, 2004 2:40 PM To: Nelly Yusupova; Spamassassin Subject: Re: Errors on Start Up At 07:58 PM 8/18/2004, Nelly Yusupova wrote: >$/usr/local/bin/spamd -d --syslog-socket=inet > >I get these errors: > >getservbyname failed for tcp at /usr/local/bin/spamd line 282 >udp connect: nobody listening at /usr/local/bin/spamd line 282 >getservbyname failed for tcp at /usr/local/bin/spamd line 290 >udp connect: nobody listening at /usr/local/bin/spamd line 290 >failed to setlogsock(inet) on this platform; reporting logs to stderr >spamd is now running > > >Is there a way to fix this? Sounds like your syslogd isn't listening over inet sockets. Reconfigure syslogd to support inet sockets, or specify the correct socket type. (Why are you specificaly using inet in the first place, instead of the normal unix domain sockets that most things use for syslog??)
