Matthew Gregan wrote:
At 2005-01-21T14:59:26+1300, Douglas Royds wrote:
Another half hour down, and no visible change. I'm going to have to nuke it.
Obviously it's not visibly making any progress, but is it using any CPU, accessing the disk, or anything of the sort? It might be useful to attach to the hung process (mozillla, was it?) with gdb or strace and see what's going on.
What should I do?
Kill the hung process and the packaging system will continue configuring all of the packages that don't depend on the package that failed to configure. At that point, you're likely to have an inconsistent system to some degree. You'll need to work out why the package hung during the configure stage, find a solution, and then reconfigure it and any other 'broken' packages (which consists of running apt-get in 'fix broken' mode).
Cheers,
-mjg
Good advice, but...
Just this afternoon I assumed that my fresh install of FC3 had hung whilst updating using the default up2date graphic interface. When I aborted it and used yum upgrade/update ( how apt-esque! ) I found that it was actually 75% through the process. No harm's done in aborting, but nasturtiums may be being cast.
Cheers,
Steve
