pkgsrc/sysutils/memtester, branch pkgsrc-2004Q4

Update to 4.0.4. From the changelog:

2004-09-02T02:30:19Z

-make memtester's exit code meaningful. See the manpage for its meaning. Thanks to Wurzel Parsons-Keir, who sent a patch for the code, so I only had to document it.

Update to 4.0.3. From the changelog:

2004-08-21T06:59:22Z

-small changes to enable building with dietlibc and a few other environments that don't even attempt to provide the various Posix definitions. -cosmetic fixes to output. -restore the reduce-and-retry loop of memory locking from version 2.

Update checksum for modified distfile with unchanged version. The

2004-08-12T00:05:31Z

diff: "stress text" was changed to "stress test" in the man page. Noticed by kre in pkg/26619.

Cosmetic increase in whitespace (no functional change).

2004-08-10T05:20:54Z

Update to 4.0.2. From the README:

2004-08-09T20:39:53Z

The version 4 rewrite was mainly to accomplish three things: (1) the previous code was basically a hack, and was ugly. (2) to make the code more portable. The previous version required some hackery to compile on some systems. (3) to make the code fully 64-bit aware. The previous version worked on 64-bit systems, but did not fully stress the memory subsystems on them -- this version should be better at stress-testing 64-bit systems. pkgsrc changes: * Use the gzipped tarball (the bzipped one is no more). * Tweak COMMENT. * GNU make is no longer needed.

Enable pkgviews installation.

2004-07-28T16:03:47Z

Switch from the first to the third person, since neither the package

2004-07-16T01:30:36Z

maintainer nor I wrote this software.

Initial import of memtester-2.93.1 from pkgsrc-wip, contributed by

2004-07-16T00:49:20Z

with some minor changes by me. memtest is a utility for testing the memory subsystem in a computer to determine if it is faulty. The original source was by Simon Kirby . I have by this time completely rewritten the original source, and added many additional tests to help catch borderline memory. I also rewrote the original tests (which catch mainly memory bits which are stuck permanently high or low) so that they run approximately an order of magnitude faster.