[Bug 218216] New: spamd frequently can't bind to port 783

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218216 Summary: spamd frequently can't bind to port 783 Product: Fedora Core Version: fc6 Platform: i386 OS/Version: Linux Status: NEW Severity: normal Priority: normal Component: spamassassin AssignedTo: wtogami(a)redhat.com ReportedBy: chris(a)chris-keane.co.uk CC: fedora-perl-devel- list@redhat.com,felicity@kluge.net,jm(a)jmason.org,parkerm @pobox.com,reg+redhat@sidney.com,wtogami(a)redhat.com The default startup priority for nfslock is 14, and for spamassassin is 78. This means that rpc.statd is started up before spamd. I'm regularly finding that rpc.statd decides to bind to port 783, which then means spamd is unable to bind to that port and exits with "spamd: could not create INET socket on 127.0.0.1:783: Address already in use". This in turn means I get swamped with spam! I'm not sure whether this is primarily an issue with rpc.statd or with spamassassin, but it'd be good to be able to persuade rpc.statd not to steal that port before spamd gets a chance to bind to it. Is this occurring because spamd doesn't have an entry in /etc/services, or would that make no difference? Changing the startup priorities so that spamd starts up before rpc.statd would be a workaround, but it's a hack. There must be a better solution. Using spamassassin-3.1.7-1.fc6 and nfs-utils-1.0.10-4.fc6. Thanks. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.