Manualshelf

HP CIFS Server 3.0c Release Note version A.02.01.02

ManualsBrandsHP ManualsSoftwareHP-UX Common Internet File System (CIFS) Client/Server Software
21222324252627282930
HP CIFS Server Release Note
Behavior Differences Between HP CIFS Server A.01.* and A.02.*
Chapter 1 21
Behavior Differences Between HP CIFS
Server A.01.* and A.02.*
Many known changes in behavior between HP CIFS Server A.01.*, based
on Samba 2.2, and HP CIFS Server A.02.*, based on Samba 3.0, might
affect your HP CIFS Server operation. This section describes significant
changes in behaviors for HP CIFS Server A.02.*. For additional changes
and details, refer to /opt/samba/SAMBA_WHATSNEW.txt.
The major changes in behaviors for HP CIFS Server A.02.01 are as
follows:
• HP CIFS Server system resource requirement has been increased
The HP CIFS Server A.02.* requires 1000 KB per smbd process.
In addition to the base memory increase, a single smbd process may
temporarily use up to 4 MB of memory swap space.
The nfile number increases from 24 to 28 entries per smbd process.
Refer to the Chapter 2, “Installing and Configuring HP CIFS
Server”, and Chapter 12, “HP -UX Cconfiguration for HP CIFS” in
the HP CIFS Server Administrator’s Guide for details.
• As of the A.02.*, the smb.conf variable strict locking default has
been changed to yes.This changes the Samba locking behavior to
check for locks on every read and write, which may affect
performance. If a change in performance is noticed, try setting
strict locking = no.
• When operating as a member of a Windows domain, A.01.* maps any
users authenticated by the remote domain controller to the guest
account if it can not obtain a UID via the getpwnam() call. A.02.*
simply rejects the connection as the NT_STATUS_LOGON_FAILURE
error.
• When adding machine accounts to an HP CIFS Server A.01.* acting
as a domain controller, you specify the add user script parameter
to create the HP-UX identity of the machine trust account. HP CIFS
Server A.02.* introduces a new add machine script parameter that
must be specified for this purpose. A.02.* does not fall back to use the
add user script option in the absence of an add machine script
option.