Package: portmap Version: 6.0-9 Severity: wishlist One problem that can occur with NFS / portmap is a lack of a loopback interface.
If there is no loopback interface, almost everything on a typical server works except for boot up hanging at starting statd, shutdown hanging at stopping portmap, and during operation running ntpq will fail to connect to a running NTP. (obviously NTP isn't your thing, but its the only other symptom of a missing loopback that I could find) Some examples of problems relating to a lack of a loopback address: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348373 Some more detail, of possible usefulness, available in my blog post at http://vincemulhollon.blogspot.com/2009/01/debian-nfs-root-interface-configuration.html Maybe an active check would be too intrusive, perhaps something a bit more passive like grep the output of ifconfig to see if there is a Loopback and if none, then echo out an error at the start of the init.d scripts. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) 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 portmap depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii libc6 2.7-18 GNU C Library: Shared libraries ii libwrap0 7.6.q-16 Wietse Venema's TCP wrappers libra ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip portmap recommends no packages. portmap suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
