On Tuesday 10 April 2018 03:52:55 to...@tuxteam.de wrote: > On Mon, Apr 09, 2018 at 06:25:34PM -0700, David Christensen wrote: > > [...] > > > One editor failing would also make me suspect the editor. > > > > > > But two failing editors would make me suspect some common factor, > > such as a shared library and/or the kernel. > > > > > > Have you tested your hardware -- power supply, memory, and SSD? Be > > sure to test the SSD before you touch any cables. If it fails, > > re-seat and/or replace cables and test again. > > Folks: you're barking up the wrong tree. *If* some editor fails > to write to a file because the hard disk goes on strike, chances > are that you'll hear your OS *SCREAM LOUDLY* that something is > wrong. > > The most typical symptom would be that the file system gets remounted > read-only because of write errors. And you tend to notice that. > Does the mount command report that? It did not.
> Cheers > -- tomás -- Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
