Package: fam Version: 2.7.0-16 Severity: normal
This morning I noticed an error while booting the computer, SpamAssassin could not be started because the port 783 was already in use. netstat -antp showed that famd was using the port. Upon restart of famd (/etc/init.d/fam restart) another port was claimed for famd, and SpamAssassin could use its claimed port. According to /etc/services the port 783 is reserved for spamd. Shouldn't famd use a port that is not claimed, or perhaps even a port in the unprivileged range (1024+)? With kind regards, Roland Clobus -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fam depends on: ii libc6 2.10.1-5 GNU C Library: Shared libraries ii libgcc1 1:4.4.1-4 GCC support library ii libstdc++6 4.4.1-4 The GNU Standard C++ Library v3 ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii portmap 6.0.0-1 RPC port mapper ii update-inetd 4.35 inetd configuration file updater fam recommends no packages. fam suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
