Running Generated Test Applications

The ConnectSMB build will generate the following test applications and install them at /usr/local/bin/openfiles:

• of_core/test/test_stream
• of_core/test/test_waitq
• of_core/test/test_fs_linux
• of_core/test/test_all
• of_core/test/test_timer
• of_core/test/test_thread
• of_core/test/test_event
• of_core/test/test_path
• of_core/test/test_dg
• of_core/test/test_iovec
• of_core/test/test_perf
• of_core/test/test_pipe
• of_core/test/test_subpersist
• of_smb_fs/test/test_fs_smb

Note

There are a set of smb file applications that are installed as a part of another package smbcp. See SMB Applications.

test_all will run tests contained within the other test applications. The individual test applications (other than test_all) are designed to test specific functionality provided by ConnectSMB.

By default, ConnectSMB will use a persistent runtime configuration. There are preconfigured runtime templates in the config subdirectory. There are default configurations based on the first three components of the build tuple. For instance, for the build tuple linux-nodebug-smbclient-openssl-nojni, the default runtime configuration is linux-nodebug-smbclient. When the product is installed the default runtime configuration is installed as /etc/openfiles.xml.

When the ConnectSMB library is initialzed, it will look at the OPEN_FILES_HOME environment variable. If set, it will look at that path for the runtime configuration. If not set it will look at /etc/openfiles.xml.

To set the runtime configuration, execute the following prior to running the program that has linked with the ConnectSMB stack:

export OPEN_FILES_HOME=./configs/darwin_debug.xml