errors from ./configure

Neil Hoggarth neil.hoggarth at
Tue Sep 26 10:54:19 GMT 2000

On Mon, 25 Sep 2000, Urban Widmark wrote:

> On Mon, 25 Sep 2000, Peter Bouton wrote:
> > ERROR: No locking available. Running Samba would be unsafe
> ... but one way to get that message is if you are running linux and do not
> have the right kernel headers in /usr/include/{linux,asm} (usually a
> symlink to /usr/src/linux).

A couple of other things that sometimes trip this warning:

1. Some platforms appear to need you to be root when running configure,
   whereas many admins do the "./configure; make" part of the process as
   a normal user and only su to root for "make install". Try re-running
   ./configure as root.

2. Sometimes this is seen if the Samba source tree is on an NFS file
   system and NFS locking isn't working properly (in which case the
   warning is valid if (and only if) you plan to use Samba to serve up
   files that you obtain via NFS (which is a silly idea - put Samba on
   the NFS server, rather than the NFS client)).

   If the source tree is on NFS, but you *don't* plan to re-export NFS
   filesystems using Samba, then move the Samba source tree to a local
   filesystem and try re-running ./configure.

Neil Hoggarth                                 Departmental Computer Officer
<neil.hoggarth at>                   Laboratory of Physiology                  University of Oxford, UK

More information about the samba mailing list