Package: portmap
Version: 5-20
Severity: important
Tags: d-i

During a new installation I noticed that the installation was "hanging" 
for quite a while during the installation of portmap (about 3 minutes as 
you can see from the log snippet below).
A 'ps alx' on VT2 showed that 'rpcinfo -p' was being executed (probably 
piped into 'grep "\(tcp\|udp\)" | grep -v portmapper | wc -l').

<snip>
Aug  2 01:19:31 in-target: Setting up portmap (5-20) ...
Aug  2 01:19:31 debconf: Obsolete command TITLE Configuring portmap called
Aug  2 01:22:41 in-target:
Aug  2 01:22:41 in-target: Setting up ucf (2.0012) ...
</snip>

(The "debconf: Obsolete command ..." line is harmless and can be ignored.)

I get the same lack of responsiveness if I later 'chroot /target' and 
execute 'rpcinfo -p' there.

A full log of the installation up to package selection is attached.

The installation is current Etch Debian Installer on i386 (vmware). 
portmap is installed as part of the "Standard" task.

Attachment: syslog-portmap.gz
Description: GNU Zip compressed data

Attachment: pgpkgU5JAGyvQ.pgp
Description: PGP signature

Reply via email to