samba - Apr 2004 - Upgraded to 3.0.2a but...

Hi folks :-)

I've just downloaded Samba 3.0.2a, run ./configure , make and make install.
All seemed to go OK but my system still appears to be running the previous
2.2.8a version.

New installation seems to have placed smbd, nmbd and swat into
/usr/local/samba/sbin (older ver was in /usr/sbin) so I changed the entries
in /etc/rc.d/rc.samba to show correct path and now smbd/nmbd are not running
at all.  Also, where is swat started from ?

All this is running on Slackware 8.

I have restarted the whole system but no luck.

What have I done wrong this time !  Fairly new to linux/samba I'm afraid.

Many thanks

Mike

> New installation seems to have placed smbd, nmbd and swat into
> /usr/local/samba/sbin (older ver was in /usr/sbin) so I changed
> the entries in /etc/rc.d/rc.samba to show correct path and now
> smbd/nmbd are not running at all.
So a "/etc/rc.d/rc.samba start" fails?

Or if it's just not started after boot, do you have a symlink in your
rc5.d or whatever runlevel you start in?  In RH/SuSE systems this is
done with chkconfig, not sure what tool Slackware uses for its "runlevel
management".
> Also, where is swat started from ?
Usually xinetd (or inetd).
> All this is running on Slackware 8.
> 
> I have restarted the whole system but no luck.
> 
> What have I done wrong this time !  Fairly new to linux/samba I'm
afraid.

Good luck,
~ Daniel














-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.

> Seems that the 3.0.2a installation put most of the files in different
> directories from the original 2.2.8a (which came bundled with this
> slackware 8).
This can be changed with --prefix statements in your ./configure step,
if you want something other than /usr/local.  Alternatively, you can
look for a Samba 3.0.2a Slackware package to upgrade to, which should
have all the ./configure stuff already set up similarly to how it was in
2.2.8a.
> The rc.samba file would not start nmbd or smbd and I couldn't manually
> start
> them from anywhere except when I went right into the
/usr/local/samba/sbin
> directory !
Did it install new startup scripts under the /usr/local/ tree?
> When I did start them I was still being told I was running
> Samba 2.2.8a.
This is after updating the rc.samba file to point to the new samba3
binaries?
> Thanks also for reminding be where swat was called from :-)  Doesn't
seem
> to
> be a "chkconfig" here.
Chkconfig is more or less a tool to create the symlinks from rc5.d (or
whichever runlevel) to the appropriate rc.d scripts.  You could do much
of the same things yourself with ln -s, but if those scripts don't start
up the correct samba version anyway, it won't help you.
> As it was causing me problems and I'm new to Linux/Samba I've just
> reverted
> back to 2.2.8a.  All seems to be running Ok, just wish there was some
way
> of
> now removing everything that the 3.0.2a installation has left behind -
> just
> to keep things tidy :-)
If you'd rather just stick with 2.2.8a you can "make uninstall"
from the
same directory you did the make install for Samba 3 to tidy up.

~ Daniel














-----------------------------------------------------------------------

This message is the property of Time Inc. or its affiliates. It may be
legally privileged and/or confidential and is intended only for the use
of the addressee(s). No addressee should forward, print, copy, or
otherwise reproduce this message in any manner that would allow it to be
viewed by any individual not originally listed as a recipient. If the
reader of this message is not the intended recipient, you are hereby
notified that any unauthorized disclosure, dissemination, distribution,
copying or the taking of any action in reliance on the information
herein is strictly prohibited. If you have received this communication
in error, please immediately notify the sender and delete this message.
Thank you.