I have just taken over a redhat system with Samba 3.0.0 configured
with security = user, and domain logins enabled. I've included the
smb.conf at the end of this message.
I would like to upgrade to 3.0.10 for a numbers of reasons, one
being security and one being that password changes don't work
from workstation machines because of the Windows KB828741
patch. What I want to know, is if I should expect any
incompatibilities between versions or if my existing config
files will work with the new version? This is a mission
critical system, so I really don't want to upgrade unless
there are going to be very minimal issues.
Will a simple rpm -Uvh ./samba-3.0.10-1_rh9.i386.rpm put me
in the clear?
Thanks for your help.
Here is some information about the system:
----- OLD RPM PACKAGE -----
$ rpm -qi samba
Name : samba Relocations: /usr
Version : 3.0.0 Vendor: (none)
Release : 2 Build Date: Thu 09 Oct 2003
05:12:20 PM PDT
Install date: Sat 11 Oct 2003 10:41:04 PM PDT Build Host: *removed*
Group : Networking Source RPM:
samba-3.0.0-2.src.rpm
Size : 46416163 License: GNU GPL version 2
Packager : Gerald Carter [Samba-Team] <jerry@samba.org>
Summary : Samba SMB client and server
----- NEW RPM PACKAGE -----
$ rpm -qpi ./samba-3.0.10-1_rh9.i386.rpm
Name : samba Relocations: /usr
Version : 3.0.10 Vendor: Samba Team
Release : 1 Build Date: Wed 15 Dec 2004
02:04:19 PM PST
Install date: (not installed) Build Host: rh9
Group : Networking Source RPM:
samba-3.0.10-1.src.rpm
Size : 45453218 License: GNU GPL version 2
Packager : Gerald Carter [Samba-Team] <jerry@samba.org>
Summary : Samba SMB client and server
----- smb.conf file -----
[global]
netbios name = *removed*
workgroup = *removed*
preferred master = yes
domain master = yes
wins support = yes
os level = 85
encrypt passwords = yes
interfaces = eth0
hosts allow = *removed*
invalid users = bin daemon adm sync shutdown
logon path logon drive = U:
logon script = logon-%G.bat
add machine script = /usr/sbin/useradd -d /dev/null -s
/bin/false -c 'Machine Account' -M %u
admin users = @smbadmin
printer admin = @smbadmin
domain logons = Yes
min protocol = NT1
[homes]
comment = User Directory
path = /usr/export/home/%U
read only = NO
browseable = NO
# only user = %S
[netlogon]
comment = Network Logon Service
path = /etc/samba/netlogon
guest ok = yes
browseable = no
[print$]
path = /var/samba/printers
write list = @smbadmin
guest ok = yes
[printers]
comment = All Printers
path = /tmp
guest ok = Yes
printable = yes
printing = lprng
browseable = No
--
Brent Smith <samba@nextreality.net>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brent Smith wrote: | | I have just taken over a redhat system with Samba 3.0.0 configured | with security = user, and domain logins enabled. I've included the | smb.conf at the end of this message. | | I would like to upgrade to 3.0.10 for a numbers of reasons, one | being security and one being that password changes don't work | from workstation machines because of the Windows KB828741 | patch. What I want to know, is if I should expect any | incompatibilities between versions or if my existing config | files will work with the new version? This is a mission | critical system, so I really don't want to upgrade unless | there are going to be very minimal issues. | | Will a simple rpm -Uvh ./samba-3.0.10-1_rh9.i386.rpm put me | in the clear? Should be fairly painless. However, make sure you read the WHATSNEW for 3.0.10 and earlier release to review any semantics changes (particularly the ones in 3.0.2a re: the password LCT). Also make sure you backup the necessary files in $(lockdir)/*tdb prior to the upgrade just in case you need to rollback. cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB/jjcIR7qMdg1EfYRAk91AKC51I0v+MblEUwsBkY1eZDgW6nXeACeKdy7 uYpNUv/gxhUJLC6u/1IM2h0=/FLt -----END PGP SIGNATURE-----