summaryrefslogtreecommitdiff
path: root/sysutils/memtester
AgeCommit message (Collapse)AuthorFilesLines
2007-05-28Update to 4.0.7. From the changelog:schmonz2-6/+6
-fix a bug in the align-to-page logic which may have prevented memtester from mlock()ing the memory it was trying to test on some systems. Thanks: Baif Chen.
2007-01-11Update to 4.0.6. From the changelog:schmonz2-7/+7
- test algorithm improvement: the walking 0 bits test was only walking the 0 bit in one direction, instead of walking it up and back down the line the way it was intended to. Thanks: Tim Rule. - formatting cleanups.
2007-01-07Mechanically replaced man/* with ${PKGMANDIR}/* in the definition ofrillig1-3/+3
INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with ${PREFIX}/${PKGMANDIR}. Fixes PR 35265, although I did not use the patch provided therein.
2005-11-01NOT_FOR_PLATFORM Interix, as it has no m[un]lock(2).tv1-1/+3
2005-08-24Introduce DJB_MAKE_TARGETS boolean, on by default, off in theschmonz1-3/+2
following packages because they don't use "it" and "setup check" as BUILD_TARGET and INSTALL_TARGET, respectively: devel/bglibs mail/mailfront mail/qmail-qfilter sysutils/memtester sysutils/qlogtools Since there's only one consumer of BGWARE_INSTALLER, and future bgware will use bg-installer from bglibs, move the do-install routine directly into qlogtools.
2005-08-07Convert to use djbware.mk.schmonz1-5/+5
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-03-22Update to 4.0.5. From the changelog:schmonz2-6/+10
-change to the method of allocating and locking memory; if we get EPERM when trying to mlock(), reset the amount of memory desired to the original amount and try again without mlock(). The reason for this is that on many systems, mlock() won't return EPERM until after having returned ENOMEM for a larger amount. The new behaviour allows processes without mlock privileges to still test the fully-specified amount or as much memory as can be allocated. Thanks for the suggestion and testing to Dan Bradley.
2005-02-24Add RMD160 digests.agc1-1/+2
2005-02-16HOMEPAGE moved. Take MAINTAINER for queue_repair at author'sschmonz1-2/+2
months-ago request.
2005-02-04Take MAINTAINER at author's long-ago request. No response fromschmonz1-2/+2
previous maintainer within two weeks.
2004-09-02Update to 4.0.4. From the changelog:schmonz2-5/+5
-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.
2004-08-21Update to 4.0.3. From the changelog:schmonz2-5/+5
-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.
2004-08-12Update checksum for modified distfile with unchanged version. Theschmonz1-3/+3
diff: "stress text" was changed to "stress test" in the man page. Noticed by kre in pkg/26619.
2004-08-10Cosmetic increase in whitespace (no functional change).schmonz1-7/+7
2004-08-09Update to 4.0.2. From the README:schmonz3-14/+15
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.
2004-07-28Enable pkgviews installation.schmonz1-3/+7
2004-07-16Switch from the first to the third person, since neither the packageschmonz1-5/+5
maintainer nor I wrote this software.
2004-07-16Initial import of memtester-2.93.1 from pkgsrc-wip, contributed byschmonz4-0/+34
<pancake at phreaker.net> 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 <sim@stormix.com>. 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.