up2date locking up?!?

[Alexander Dalloz]

Am Mi, den 27.07.2005 schrieb Andrew Stewart um 15:18:

> So I started up2date and opted to just update /everything/, and left it 
> over night.  Coming back, I see that it has locked up, or has apparantly 
> locked up.

It would be helpful to know little more about the update process. What
packages to be updated? How much packages in total? Is it a fresh FC3
install (full or minimal install then) getting all updates? Where does
the up2date job ended: in download state or in install of packages
state?

> Anyone seen this?  Should I be worried about killing the process?  
> Should I just reinstall FC3?

No, this is not Windows.
You can kill the process, yes.
Different strategies can make sense. If you are updating a many packages
it makes sense to not update them all in one single step. It too may be
wise to run up2date-nox in runlevel 3.

> -Andrew

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp 
Serendipity 15:26:16 up 11 days, 19:58, load average: 0.20, 0.19, 0.12 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20050727/9a491ff6/attachment-0001.sig>