In your situation, I'd check the size of the swap partition and make sure it was equal to the amount of ram on my machine. I'd also check the /tmp partition and find out how full it is after one of these failures. It's possible you're out of virtual memory not physical memory. I'd also check how full the directory tree is where trn stores my articles. If I could find sighted assistance that knew what memtest86 was and how to interpret it, I'd have the computer tested with that too just to be sure none of my physical memory hadn't gone out or was about to die. On Sun, 15 Apr 2012, Hart Larry wrote: > Well, since I last asked here on a trn issue, I submitted a Debian bug which > was fixed. If I were saving or appending to a file which reached "maxint" it > would not grow any larger-and-ruin what I already received. > Well, now, granted its alot of articles, nearly 5million, after awhile with no > warning trn says, "trn out of memory, signal bye bye" Are their ways I can > examine what may be taking up memory while trn is running? > O, this is Debian 2.6.32 and trn4 test77 4 > Thanks so much in advance > Hart > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/blinux-list > > ---------------------------------------------------------------- Jude <jdashiel-at-shellworld-dot-net> <http://www.shellworld.net/~jdashiel/nj.html> _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list