~zulcss/samba/server-dailies-3.4

SSLLoadSharedLibrary: Failed to load library /<client program directory>/libcrypto.so.0.9.7:/<client program directory>/libcrypto.so.0.9.7: cannot open a shared object file: No such file or directory.

The fix found on the VMware knowledge base (search http://kb.vmware.com for

Doc ID: 1837104) states that it's a known problem with the scripting libraries,

and can be resolved by installing VMware Server on the host, which properly

sets up the SSL module loader. This is what I would suggest if you encounter

this, as it solved the problem for me (I don't have VMware Server actually

running on that host though).

INSTALLATION

To use these scripts, modify initial_setup.conf to match your environment. The

GUEST_HOSTNAME, GUEST_WORKGROUP, HOST_SERVER_NAME, HOST_SERVER_PORT,

HOST_USERNAME, and HOST_PASSWORD variables are optional, and are commented out

in this release.

Running initial_setup.sh will:

* Get the IP address of the Windows guest VM.

* Take a snapshot of the pristine Windows guest.

* Copy the windows scripts from the windows-scripts directory on the unix host

to the directory on the Windows guest specified by the

GUEST_SCRIPT_PATH option. This path will be created on the guest if

it does not already exist.

* Execute win_setup.wsf on the Windows guest in order to create the

administrator account specified by GUEST_USERNAME and GUEST_PASSWORD,

enable and start the telnet service, and set the GUEST_HOSTNAME and

GUEST_WORKGROUP if configured.

* If these operations are successful so far, another snapshot is taken at this

point. This is the snapshot which is restored if the tests encounter

problems they are unable to recover from.

These operations leave the Windows guest in a state such that it can be

remotely administered with telnet. Specifically, this will allow us to use

'make wintest' in Samba 4 to perform smbtorture tests against a Windows host,

and perform tests from a Windows client to a Samba server.

INTEGRATING WITH THE BUILD FARM

Follow the standard steps to add a host to the build farm. The major

difference is that we will need to run these tests as root. To run the

Windows tests in the build farm, a .fns file will need to be created for

your new host that exports a WINTESTCONF environment variable pointing to a

config file used by 'make wintest'. An example of this config file can be

found at source/selftest/win/test_win.conf in the Samba 4 source tree.

I've also included the bnhtest.fns file that I'm using for my build farm host

below, as an example. It was modified from generic.fns.

action_test_windows() {

do_make wintest

w_status=$?

echo "WINTEST STATUS: $w_status"

return $w_status;

}

per_run_hook

system=`uname`

export WINTESTCONF="/home/build/win/test_win.conf"

for compiler in gcc cc icc; do

100

# arrgh, "which" gives no err code on solaris

101

path=`which $compiler`

102

if [ -x "$path" ]; then

103

104

if $compiler -v 2>&1 | grep gcc.version > /dev/null; then

105

isgcc=1

106

CFLAGS="-Wall"

107

export CFLAGS

108

else

109

CFLAGS=""

110

export CFLAGS

111

isgcc=0

112

113

if [ $compiler = gcc -o $isgcc = 0 ]; then

114

115

# only attempt samba4 if we have perl

116

if which perl > /dev/null; then

117

test_tree samba4 source $compiler configure build install test_windows test

118

119

120

121

done