All: Before I actually go and take the plunge on performing this upgrade I would like to find out if there are any caveats I should be aware of. I am using RedHat 7.3 and have been using the pre-installed Samba since I began upgrading our network to Samba about 4 months ago. I plan on using the 2.2.7a rpm from Samba.org and would like to know if any of you have done this and whether or not you ran into problems and if so what was the best way to go about fixing them. My plan is to run: /etc/rc.d/init/smb stop rpm -e samba-client rpm -e samba rpm -e samba-common and then run rpm -ivh samba-2.2.7a.i386.rpm /etc/rc.d/init/smb start My main concern is with the people who are currently logged into the server. Do I need to be sure that everyone is logged out? Or will they be logged out automagically when I shutdown the daemon. If there is a preferred way to go about the upgrade than what I have above, please let me know. I am including my smb.conf in hopes that if someone spies something awry they will let me know. I look forward to any input, Thanks A Cline [global] ;basic server settings workgroup = CRHDOM netbios name = CRHPDC server string = Cushing PDC socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 guest account = nobody ;Standard printing settings printing = BSD print command = /usr/bin/lpr -P%p -r %s lpq command = /usr/bin/lpq -P%p lprm command = /usr/bin/lprm -P%p %j min print space = 2000 ;PDC and master browser settings os level = 64 preferred master = yes local master = yes domain master = yes ;Security and Logging Settings security = user encrypt passwords = yes #update encrypted = yes passwd chat debug = yes domain logons = yes log file = /var/log/samba/log.%m log level = 2 max log size = 50 hosts allow = 127.0.0.1 172.29.56.0/255.255.252.0 ;User profiles and home directory #logon home = \\%L\%U\.profile logon drive = R: logon path = \\%L\profiles\%U logon script = %U.bat add user script = /usr/sbin/useradd -d /dev/null -g smbmachines -s /bin/false -M %u domain admin group = @smbadmins cpatter sharriso ;Password Syncronization unix password sync = yes passwd program = /usr/local/bin/smbpasswd %u passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* pam password change = Yes #domain group map = /etc/samba/group.mapping #==Shares= [homes] comment = Home Directories browseable = no writable = yes admin users = @smbadmins [profiles] path = /home/samba/profiles guest ok = yes browseable = no read only = no create mask = 0600 directory mask = 0700 share modes = no ;nt acl support = no [netlogon] browseable = no path = /home/netlogon root preexec = perl /root/mklogonscript.pl %u %m %a [etime] path = /home/samba/etime browseable = no read only = yes create mask = 0660 directory mask = 0770 write list = @etime @smbadmins force group = etime admin users = acline bob bmyers [financials] path = /home/samba/financials create mask = 0660 directory mask = 0770 browseable = no read only = yes write list = @financials @smbadmins admin users = acline bob bmyers force group = financials [123work] path = /home/samba/lotus create mask = 0660 directory mask = 0770 browseable = no read only = yes write list = @lotus @smbadmins admin users = @smbadmins force group = lotus [vp10] path = /home/samba/vp10 create mask = 0660 directory mask = 0770 browseable = no read only = yes write list = @vp10 @smbadmins admin users = @smbadmins force group = vp10 [mrms] path = /home/samba/mrms create mask = 0660 directory mask = 0770 browseable = no read only = yes write list = @mrms @smbadmins admin users = @smbadmins force group = mrms [product] path = /home/samba/product create mask = 0660 directory mask = 0770 browseable = no read only = yes write list = @product @smbadmins admin users = @smbadmins force group = product [software] path = /home/samba/software create mask = 0660 directory mask = 0770 browseable = no read only = yes write list = @smbadmins admin users = @smbadmins force group = smbadmins [backup] path = /home/samba/backup create mask = 0660 directory mask = 0770 browseable = no read only = yes write list = @smbadmins admin users = @smbadmins force group = smbadmins [printers] guest ok = yes printable = yes guest account = ftp use client driver = yes _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
Le 30/01/2003 02:01, ??A Cline?? <acline27@hotmail.com> a ?crit?:> All: > > Before I actually go and take the plunge on performing this upgrade I would > like to find out if there are any caveats I should be aware of. I am using > RedHat 7.3 and have been using the pre-installed Samba since I began > upgrading our network to Samba about 4 months ago. I plan on using the > 2.2.7a rpm from Samba.org and would like to know if any of you have done > this and whether or not you ran into problems and if so what was the best > way to go about fixing them.*** You will probably have dependency problems with the rpm's. <snip>> My plan is to run: > > /etc/rc.d/init/smb stop > rpm -e samba-client > rpm -e samba > rpm -e samba-common > > and then run > > rpm -ivh samba-2.2.7a.i386.rpm > /etc/rc.d/init/smb start*** Why? What happened to rpm -Uvh samba.rpm? What you should do, according to me, is sava the samba config dir. Hell, tar the whole /etc dir to have a backup while you're at it, then do a rpm -Uvh --test samba.rpm to test the update and see if you need libs etc. Then fix a date and inform your users about the expected downtime. The day of the update check nobody is connected with smbstatus, do a /etc/init.d/smb stop update samba, untar your samba conf files into /etc, start samba and test the connection. If OK mail your users, if KO run very fast and very far... ;-))) In order to cut down on downtime for your users you should do the update either at night or week-ends.> My main concern is with the people who are currently logged into the server. > Do I need to be sure that everyone is logged out? Or will they be logged > out automagically when I shutdown the daemon.*** See above. I wouldn't shutdown samba without telling your users.> I am including my smb.conf in hopes that if someone spies something awry > they will let me know.<snip> Cheers, Zoran.