On Fri, Jun 10, 2011 at 03:58:45AM +0200, Vincent Lefevre wrote: > On 2011-06-10 03:49:28 +0200, Vincent Lefevre wrote: > > Is it a bug in spamassassin (that did a special request to famd and > > forgot about it) or in famd (but why would it listen to port 783)? > > The problem comes from the fact that famd chooses a random port at > startup. > > I don't know what is the policy for port selection, but either > spamd should choose a different port until it succeeds, or (if > ports are supposed to be fixed) this should be seen as a critical > bug of famd, because its choice potentially breaks other packages > (like spamassassin).
sh-4.1$ egrep '\s783' /etc/services spamd 783/tcp # spamassassin daemon The bug is with famd. It wouldn't make sense for spamd to choose a different port, because clients would have no way of knowing what it is. famd (last I knew anyway; I haven't touched it in years) uses portmap, so it can choose an arbitrary port. noah
signature.asc
Description: Digital signature
