SMB Traffic Analyzer 1.2 released
We just released SMB Traffic Analyzer version 1.2.
After the release of version 1.1 we got immediate feedback that the configuration file is not being read correctly. The port number to connect to the VFS module was overwritten when a client port number was given (bnc#652755), in case a configuration file was used with smbtad.
The smbtad daemon can now use unix domain sockets instead of an internet socket. This feature is useful in the case smbtad is running with the Samba server on the same machine. In this situation, a unix domain socket is much easier to configure and likely much faster than connecting via internet socket to localhost (bnc#651890). Unix domain sockets are also very handy for our plan to create appliances for SMB Traffic Analyzer.
smbtaquery is now able to interpret more detailed object specifications, such as:
"file testfile, share pool"
This object declaration would then check the database for the file “testfile”, which is on the share “pool”. With previous versions of smbtaquery, and given you would have more files names “testfile” on different shares, the identification function of SMBTA would have asked you for the right file. By giving more objects in a row, the user can now specify a unique object on the command line (bnc#650548).
smbtaquery is now able to read commands from a file with the ‘-f’ argument. Therefore planned statistics can now be issued scripted. The initial implementation is very simple and just allows for comments and commands (bnc#653611). A typical file might look like this:
# example smbtaquery command file # Show the global usage of the Samba network global, usage rw; # # Show the sum of bytes written by user 'holger' user holger, total w;
The documentation has been update to reflect all the changes in these bugs.