I have executed
./configure --with-lockdir=/var/lock/samba
and get a proper Makefile with
LOCKDIR = /var/lock/samba
The trouble is
strings ./usr/sbin/smbd | grep /var/lock
reports
/var/lock
not the expected /var/lock/samba! There are no entries for "lock
dir" or "lock directory" in smb.conf, and true to fashion
testparm -s | grep "lock dir"
reports
lock dir = /var/lock
?! How come !?
For the record, the full configure command is:
./configure \
--with-fhs \
--prefix=/usr \
--localstatedir=/var \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--sysconfdir=/etc \
--with-configdir=/etc/samba \
--with-privatedir=/etc/samba/private \
--with-codepagedir=/etc/codepages \
--with-lockdir=/var/lock/samba \
--with-smbmount \
--with-quotas \
--with-syslog \
--with-utmp \
--with-netatalk \
--with-sambabook=/usr/share/swat/using_samba \
--with-ssl \
--with-sslinc=/usr/include/openssl \
--with-msdfs \
--with-vfs \
i386-slackware-linux
Other than the above problem, everything works as advertised!
Charlie Wilder wrote:> > I have executed > > ./configure --with-lockdir=/var/lock/samba > > and get a proper Makefile with > > LOCKDIR = /var/lock/samba > > The trouble is > > strings ./usr/sbin/smbd | grep /var/lock > > reports > > /var/lock > > not the expected /var/lock/samba! There are no entries for "lock > dir" or "lock directory" in smb.conf, and true to fashion > > testparm -s | grep "lock dir" > > reports > > lock dir = /var/lock > > ?! How come !?I noticed that - we seem to have all the configure magic, but don't actually use it... Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net