pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2008-05-01	Update dbench to 3.04.	obache	1	-5/+5
	Changes is unknown. While here, * install README file mentioned in man page, suggested in PR 38553. * move client.txt to subdir noted in man page * fix directory of those files in man page.
2006-03-16	Make this package build on Darwin. getxattr(2) and setxattr(2) on Darwin	minskim	1	-2/+2
	require additional arguments related to the resource fork attribute.
2005-11-06	Use O_FSYNC instead of O_SYNC on DragonFly. Disable extattr_get_file	joerg	1	-2/+3
	on DragonFly, the semantic is different and it isn't very useful in the current form.
2005-10-10	Explicitly specify to Makefile.in the directory on which the manpages	xtraeme	1	-1/+2
	will be installed, otherwise as --mandir now defaults to ${PREFIX}/${PKGMANDIR}, they won't be installed into the correct location. Bump PKGREVISION.
2005-09-25	Added a chunk to patch-aa that comments out unnecessary code (statvfs). Now	rillig	1	-2/+2
	the package builds on NetBSD-1.6.2. Bumped PKGREVISION.
2005-07-12	Changes 3.03:	adam	1	-5/+4
	* Many improvements
2005-03-25	Make this package build on Darwin.	minskim	1	-1/+2
	- Include sys/aio.h to use O_SYNC. - Use fsync(2) instead of fdatasync(2), which is unavailable on Darwin.
2005-02-22	Add RMD160 digests in addition to the SHA1 ones.	agc	1	-1/+2

2004-11-10	Changes 2.1:	adam	1	-5/+4
	* unknown
2003-09-19	Make compile on Solaris. From Jonathan Perkin in PR 22858.	wiz	1	-2/+2

2003-07-17	Initial import of dbench-1.3 into the NetBSD Packages Collection.	agc	1	-0/+6
	Taken from the dbench README file: Netbench is a terrible benchmark, but it's an "industry standard" and it's what is used in the press to rate windows fileservers like Samba and WindowsNT. In order for the development methodologies of the open source community to work we need to be able to run this benchmark in an environment that a bunch of us have access to. We need the source to the benchmark so we can see what it does. We need to be able to split it into pieces to look for individual bottlenecks. In short, we need to open up netbench to the masses. To do this I have written three tools, dbench, tbench and smbtorture. All three read a load description file called client.txt that was derived from a network sniffer dump of a real netbench run. client.txt is about 4MB and describes the 90 thousand operations that a netbench client does in a typical netbench run. They parse client.txt and use it to produce the same load without having to buy a huge lab. They can simulate any number of simultaneous clients.