Problems found with existing distfile for superpi:
distfiles/super_pi-20030927/super_pi.tar.gz
No changes were made to the superpi/distinfo file.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
distfiles/eagle-lin32-7.4.0.run
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.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
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.
