Redirect default path - Samba installation with apt

Come here to share your tips and tricks for using Samba4
Locked
Totoyesyes
Messages: 1
Registration: Apr 18, 2018 - 2:59 p.m.

April 18, 2018 - 3:13 PM

Hello everyone,
I am currently working on setting up a Samba AD on my Debian 9 server.
I have already performed this installation using a ".tar.gzcommandwget, however I now need to perform the same installation using the "apt install" command.

The problem is that the paths to the configuration files and various directories in Samba differ depending on whether you use "wget" or "apt install". For example:

Path to smb.conf:
Installed via wget: /usr/local/samba/etc/smb.conf
Installed via apt: /etc/samba/smb.conf

Or the path to /bin/samba-tool :
wget: /usr/local/samba/bin/samba-tool
apt: /usr/bin/samba-tool

My goal is to make the paths generated during installation via "aptfile.tar.gzretrieved via "wget".


Thank you to anyone who has any solution or suggestion for resolving this issue.
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

April 20, 2018 - 12:23

Hello totoyesyes,
Totoyesyes wrote: Apr 18, 2018 - 3:13 PM I am currently working on setting up a Samba AD on my server running Debian 9.
I have already performed this installation using a ".tar.gz" file retrieved via the "wget" command, however I now need to perform the same installation using the "apt install" command.

The problem is that the paths to the configuration files and different directories of SaMBa differ depending on whether you use "wget" or "apt install", for example:

Path to smb.conf:
Installed via wget: /usr/local/samba/etc/smb.conf
Installed via apt: /etc/samba/smb.conf

or the path to /bin/samba-tool :
wget: /usr/local/samba/bin/samba-tool
apt: /usr/bin/samba-tool

My goal is to ensure that the paths generated during installation via "aptfile.tar.gzretrieved via "wget".
To do this, you need to recreate the Deb package.

That said, I have some questions regarding the relevance of this: either the server is a production server and it is preferable to use a deb that has been validated, or the server is a test server and we can use the targz for R&D.

But these two uses are different enough that we shouldn't have to mess with the paths, IMHO. Besides, having a production server with its daemons in /usr/local doesn't seem very elegant to me.

Sincerely,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked