netbench to the masses.
.br
Both \fBdbench\fP and \fBtbench\fP 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.
+client_enterprise.txt that was derived from a capture of a real
+netbench run. client_enterprise.txt is about 25MB and describes the
+500 thousand operations that a netbench client does in a typical
+netbench run. They parse client_enterprise.txt and use it to produce
+the same load without having to buy a huge lab.
.br
dbench produces only the filesystem load. It does all the same IO
calls that the smbd server in Samba would produce when confronted with
.TP
.B \-c client.txt
Use this as the full path name of the client.txt file (the default is
-/usr/share/dbench/client.txt).
+/usr/share/dbench/client_enterprise.txt).
.TP
.B \-s
Use synchronous file IO on all file operations.
.TP
+.B \-t TIME
+set the runtime of the benchmark in seconds
+.TP
+.B \-D DIR
+set the base directory to run the filesystem operations in
+.TP
+.B \-x
+enable xattr support, simulating the xattr operations Samba4 would
+need to perform to run the load
+.TP
.B \-S
Use synchronous IO for all directory operations (unlink, rmdir, mkdir
and rename).
should be invoked on that server before invoking \fBtbench\fP.
\fBtbench\fP can also take the following options:
.TP
-.B \-c client.txt
+.B \-c loadfile
Use this as the full path name of the client.txt file (the default is
-/usr/share/dbench/client.txt).
+/usr/share/dbench/client_enterprise.txt).
.TP
-.B \-t option[,...]
+.B \-T option[,...]
This sets the socket options for the connection to the server. The
options are a comma-separated list of one or more of the following:
.BR "SO_KEEPALIVE" ,