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 Graeme ________________________________ From: Michael Wood <[email protected]> To: Graeme Porter <[email protected]> Cc: Andrew Bartlett <[email protected]>; "[email protected]" <[email protected]> Sent: Wednesday, 17 April 2013, 12:12 Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors Hi On 17 April 2013 12:01, Graeme Porter <[email protected]> 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 <[email protected]> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
