samba - May 2004 - FYI - Why RPMs are important

Someone emailed me directly when I was asking about the 8.0 RPMs, and why I
didn't just compile it. Due to the production nature of our servers which
run practially 24/7, I can do an "rpm -Uhv samba.rpm" and then do an
"smb restart" with very little impact. If I move to non-rpm versions,
I am forced to compile first, remove the RPM, which is a longer downtime, then
install Samba and then turn Samba back on.

Just FYI. *shrug*

JMS

Of course, you can download the source RPM, then issue "rpmbuild
--rebuild samba-3.0.4-1.src.rpm" then you'd have your very own RPM
sitting in /usr/src/redhat/RPMS/i386/ which you could then install as
you say below.

This is, of course, assuming you have all the appropriate compilers
and utilities installed.

However, you'll be pleased to have this link:

http://us1.samba.org/samba/ftp/bin-pkgs/RedHat/RPMS/i386/8.0/

which is one of the many mirrors where binaries for RedHat 8.0 are
found. I just check and as of 9:28 PM PDT the 3.0.4 binary was present.

--Jon Johnson
Sutinen Consulting, Inc.
jon@sutinen.com

On Thu, 13 May 2004, Josh Skains wrote:
> Someone emailed me directly when I was asking about the 8.0 RPMs, and
> why I didn't just compile it. Due to the production nature of our
> servers which run practially 24/7, I can do an "rpm -Uhv
samba.rpm"
> and then do an "smb restart" with very little impact. If I move
to
> non-rpm versions, I am forced to compile first, remove the RPM, which
> is a longer downtime, then install Samba and then turn Samba back on.
> 
> Just FYI. *shrug*
> 
> JMS
> 
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>

Hi, Josh!

	I think there's a workaround to avoid using RPMs. When you do "smb 
restart" you are doing "smb stop" and "smb start", and
that closes alls
client connections, so you've got to stop service anyway. That's it:

	- Compile and install samba with a prefix like "/opt/samba-x.y.z"
	- ln -s /opt/samba-x.y.z /opt/samba
	- Set your new initscript like "/etc/init.d/samba" , which uses your 
new path (/opt/samba) and use it to define the passes through every run 
level.
	- Set the appropiate environment variables to your scripts to avoid 
using the ones are already working (/usr/bin or whatever) 
(PATH=/opt/samba/bin:$PATH , for example)
	- /etc/init.d/smb stop
	- /etc/init.d/samba start
	- rpm -e samba* (do it after, once the new version works fine, if you 
prefer)

	You can test it before in your development servers, something like this 
should do the work for you. Once you've done it this way you will be 
able to compile newer versions with previx = /opt/samba-x'.y'.z' and
the
restart will be just:

#!/bin/sh
/etc/init.d/samba stop
rm /opt/samba
ln -s /opt/samba-x'.y'.z' /opt
/etc/init.d/samba stop


	Theese both procedures are totally scriptable and has so few impact in 
you HA environment like using RPMs, with the goody of being using 
anytime the version that you prefer, independently of which one is RPM 
packed by your distro.


	Hope it helps!



Josh Skains wrote:
> Someone emailed me directly when I was asking about the 8.0 RPMs, and why I
didn't just compile it. Due to the production nature of our servers which
run practially 24/7, I can do an "rpm -Uhv samba.rpm" and then do an
"smb restart" with very little impact. If I move to non-rpm versions,
I am forced to compile first, remove the RPM, which is a longer downtime, then
install Samba and then turn Samba back on.
> 
> Just FYI. *shrug*
> 
> JMS
> 

-- 
Angel Galindo Mu?oz
agalindo@ub.edu