[Samba] How to determine Samba Installation directory

[Mark Foley]

On Wed, 30 Apr 2025 21:19:57 Rowland Penny <rpenny at samba.org> wrote:
>
> On Wed, 30 Apr 2025 15:40:06 -0400
> Mark Foley via samba <samba at lists.samba.org> wrote:
>
> > I'm building Samba from a scratch download from samba.org.  One of
> > the ./configure options is --prefix, which directs where to install
> > the files. 
> > 
> > The "default" is /usr/local/samba, but from experience I know my
> > distro does not put the files there. There is nothing in either my
> > /usr/lib/samba or /usr/local/samba.
> > 
> > How can I determine where my current --prefix directory is?
> > 
> > THX --Mark
> > 
>
> It is a bit more involved than that, if you just set the '--prefix'
> option, then everything will end up in whatever directory you use.
>
> You need to find out how Slackware builds Samba and build it in exactly
> the same way.
>
> Rowland

I don't think I'll be able to figure out how Slackware builds Samba.  I've done
this before many years ago and it worked, and I'll have a full backup in case
things go wrong. I do know I'll have to use --with-system-mitkrb5.

Most of the files appear to be in /var/lib/samba, including:

account_policy.tdb
account_policy.tdb.bak
bind-dns/
ntp_signd/
private/
registry.tdb
registry.tdb.bak
share_info.tdb
share_info.tdb.bak
sysvol/
winbindd_cache.tdb
winbindd_cache.tdb.bak
winbindd_privileged/

and /var/lib/samba/private:

dns_update_cache
dns_update_list
encrypted_secrets.key
hklm.ldb
hklm.ldb.bak
idmap.ldb
idmap.ldb.bak
kdc.conf
krb5.conf
ldap_priv/
ldapi=
msg.sock/
netlogon_creds_cli.tdb
privilege.ldb
privilege.ldb.bak
sam.ldb
sam.ldb.bak
sam.ldb.d/
schannel_store.tdb
schannel_store.tdb.bak
secrets.keytab
secrets.ldb
secrets.ldb.bak
secrets.tdb
secrets.tdb.bak
share.ldb
share.ldb.bak
smbd.tmp/
spn_update_list

smb.conf is in /etc/samba

samba (executable) is in /usr/sbin

I think I'll try --prefix=/var/lib/samba and see was happens!

Do you think I should clear out /var/lib/samba first or will the new build
use/keep that information (domain members, users, policies, ...)?

Will I have to provision from scratch? I can do so if needed, no problem.

I may have to rejoin domain members? I'll take them offline before doing this.

--Mark