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

Michael Wood esiotrot at gmail.com
Wed Apr 17 05:54:16 MDT 2013

On 17 April 2013 13:41, Graeme Porter <graeme.porter at yahoo.co.uk> wrote:
> The symlinks were made by entering:
> ln /usr/local/samba/sbin/samba /usr/bin/samba
> ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient

That's what I suspected :)

Those are hard links, not symbolic/soft links.

You need to use "ln -s source destination" to create symlinks.

> 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?

If you create a hard link to a file, the original file name and the
new hard link are indistinguishable from each other.  They are both
names that point to the actual file.  If you remove one of them (e.g.
by running "make install") the other one will still be there, pointing
to the original file on disk.

i.e. hard links point to the actual file.  Symbolic links are names
that point to other names.

Michael Wood <esiotrot at gmail.com>

More information about the samba mailing list