[Samba] Samba4 fails to work following upgrade - library version errors

Graeme Porter graeme.porter at yahoo.co.uk
Wed Apr 17 05:41:45 MDT 2013

The symlinks were made by entering:

ln /usr/local/samba/sbin/samba /usr/bin/samba
ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient

I realise this isn't the correct way of doing things (obviously the correct way would be to update the system PATH environment variable), but at the same time I can't see why it's a bad idea.  Unless something happens to the symlink that I wasn't expecting when the file it is linking to is removed or altered?

Kind regards

 From: Michael Wood <esiotrot at gmail.com>
To: Graeme Porter <graeme.porter at yahoo.co.uk> 
Cc: Andrew Bartlett <abartlet at samba.org>; "samba at lists.samba.org" <samba at lists.samba.org> 
Sent: Wednesday, 17 April 2013, 12:12
Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors


On 17 April 2013 12:01, Graeme Porter <graeme.porter at yahoo.co.uk> wrote:
> Hi Andrew,
> I performed another upgrade yesterday
> First a "git clean", then a "git pull", a "./configure --enable-selftest --enable-debug --enable-avahi", a "make", and finally a "make install"
> After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there.  So I had exactly the same problem as before.  I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process.

The samba build system does not copy things to /usr/bin (unless you
fiddle with things like --prefix etc.)

How exactly did you make the symlinks?

Michael Wood <esiotrot at gmail.com>

More information about the samba mailing list