[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#382070: marked as done (Long pauses during configuring portmap and configuring printconf)

Your message dated Sat, 14 Oct 2006 18:32:28 +0200
with message-id <200610141832.28878.elendil@planet.nl>
and subject line Bug#382070: Long pauses during configuring portmap and configuring printconf
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: installation-reports

I recently did a businesscard install of the etch daily.
There were two unexpectedly long pauses in the later part of the installation. I've seen these before, so they aren't just a fluke. So I'm reporting them now.
The first was during "Configuring portmap". Looking on the VT02 console, "ps" showed that it was doing "rpcinfo -p". As an experiment, I did a chroot to /target myself and tried "rpcinfo -p". It hung, though a ctl-C killed it.
The second was during "Configuring printconf". Again, looking on the VT02 console with "ps", it seemed to be doing "/usr/bin/lpstat -l -d - p -v" for a long time -- then later it was doing "/usr/bin/lpstat -d" for an equally long time.
Normally these operations take a very short time. Is there something in the configuration process that is being done out-of-order, so that a vital system component isn't available yet? 

Logs are available on request...

Rick

--- End Message ---
--- Begin Message --- 
Hello Rick,

On Tuesday 08 August 2006 18:08, Rick Thomas wrote:
> There were two unexpectedly long pauses in the later part of the
> installation.   I've seen these before, so they aren't just a fluke.
> So I'm reporting them now.

This issue has been resolved since you reported it.

Cheers,
FJP

Attachment: pgpF5XY03L1Nf.pgp
Description: PGP signature


--- End Message ---
Reply to: