[tex-live] tlmgr update --self --all crash

[Lars Madsen]

exactly

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf


________________________________________
From: Pander [pander at users.sourceforge.net]
Sent: 03 December 2012 17:00
To: Lars Madsen
Cc: Bob Tennent; Norbert Preining; tex-live at tug.org
Subject: Re: [tex-live] tlmgr update --self --all crash

On 2012-12-03 16:52, Lars Madsen wrote:
> Bob did you check the RAM in the computer?
>
> A few years ago I had a problem where I downloaded an ISO and each time I md5 tested it I got different results.
>
> Then someone suggested that I tested the RAM, and sure enough one of them failed.

Linux is very good in marking bad pages in RAM and keep on running. That
might fool one into thinking RAM is OK. Once I also had this problem.
Only running a memory test from boot will show you that someting is wrong.

> /Lars Madsen
> Institut for Matematik / Department of Mathematics
> Aarhus Universitet / Aarhus University
> Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf
>
>
> ________________________________________
> From: tex-live [tex-live-bounces at tug.org] on behalf of Bob Tennent [rdt at cs.queensu.ca]
> Sent: 03 December 2012 16:37
> To: Norbert Preining
> Cc: tex-live at tug.org
> Subject: Re: [tex-live] tlmgr update --self --all crash
>
>  >|Well, something *is* seriously broken on your computer.
>
> Only tlmgr update has been problematic over the last 5 days.
>
>  >|broken hard disk?
>
> a relatively new SSD
>
>  >|running fsck?
>
> forced on all partitions; no issues.
>
>  >|showing *how* tlmgr update --self broke?
>  >|running the update with -v -v and send the result?
>
> Thanks. I hadn't noticed the -v option before; it's not exactly obvious
> in the man page.
>
> So today I ran the update with -v -v. Of course it went smoothly :+)
> I'll do the same for a few days and if all's well assume it was some
> temporary glitch. Perhaps the re-boot cleared it.
>
> Best,
> Bob T.
>