readme0103.txt -- "1.0.3" -- minor adjustments


Release v1.0.3 is now available for use in a ZerverModule(tm)
and in ProZerver systems.


Changes.

For SMB/CIFS protocols (Samba), drop use of the default name
as an alternate node name.  The default name is derived from
six of the hexadecimal digits in one of the network interface
"MAC-Media Access Code" values, such as "X7513D0".  This is
used during boot-up, and if no other name is defined for the
node, this default name is used.  In the past, this default
name would also be defined as an alternate node name, at
least for SMB/CIFS protocol, in addition to the user-defined
node name.  This appears to lead to some ambiguity, and
some problems with addressability by name or by IP-address.
So now this default name will only be used if there is no
other name defined, and the node will not advertise itself
with two apparently equal, different, names.

For SMB/CIFS protocols (Samba), change the configuration so
that when a second samba connection comes from a given IP
address, an earlier connection from that IP address is broken.
There are conditions in which a Samba connection can be
in-use, with some number of files open, in-use and locked from
any other access, and something happens to that connection
or that client which does not break-down the connection.
Under the previous configuration, a re-connect from that
client IP-address would find those files still locked, with
no way to achieve an un-lock.  With this configuration, the
second connection from an IP-address should result in the
ending of the first connection, and thus an unlock of any
files that were being held open and locked.  Note that this
can be a bad thing if Samba connections originate from behind
an NAT-Network-Address-Translation router, in which distinct
clients would appear to be coming from a single IP-address.

When changing IP-addresses, ensure that all netbios names
get the new addresses.

Improved handling of File-System-Check and Repair operation
(which is not a "minor" change when that is what you need).
The result of a File-System-Check and Repair operation
now goes only to a temporary file displayed with the admin
web-page for Status/File-Sys-Op -- had been duplicated and
also put in the Status/Current-Details log, but this managed
to confuse the program which would check the result-code
for the Repair operation.  This improvment is made possible
by the arrival of a test disk that had some kind of HW or
interface problem, and within two hours of a stress test,
there was a File-System that was in need of Repair.

Raid-group web-page display fixed for case in which no disk
drives had any raid-group pieces, and no raid-group-handling
modules were loaded.

Change userid for web-server and some internal group
membership definitions to improve certain security operations.
The only visible result is that new directories created by
the share-create admin web page will now be owned by userid
"public" with group ownership of "everyone" -- had been userid
"public" with group ownership of "admin", as reported using
FTP access.

Component upgrades --
	linux-2.6.22.1 (had been 2.6.21.3)
	Linux-PAM-0.99.8.1 (was 0.99.7.1)
	drbd-0.7.24 (was 0.7.23) used with ZerverPair


August 20, 2007