samba - Nov 2017 - Compiling Samba 4.7 with systemd support on Fedora 26

Am 23.11.2017 um 23:16 schrieb Arnab Roy:
> No dice :( removed as suggested updated unit file looks like this
"Type=notify" can not work until systemd-support was successful built 
which does not seem to be the case looking at the starting posts!
> [Unit]
> Description=KKonnect KHIPU-NETWORKS Service
> After=syslog.target network.target
> 
> [Service]
> Environment=KRB5CCNAME=FILE:/run/samba/krb5cc_samba
> Type=notify
> NotifyAccess=all
> ExecStart=/usr/local/samba/sbin/winbindd
> ExecReload=/usr/bin/kill -HUP $MAINPID
> LimitCORE=infinity
> 
> [Install]
> WantedBy=multi-user.target
> 
> I had lifted the unit file from an rpm install of samba from fedora.
> 
> Thanks
> Arnab
> 
> On Thu, Nov 23, 2017 at 10:09 PM, Reindl Harald via samba 
> <samba at lists.samba.org <mailto:samba at lists.samba.org>>
wrote:
> 
> 
> 
>     Am 23.11.2017 um 23:03 schrieb Rowland Penny via samba:
> 
>         On Thu, 23 Nov 2017 21:46:17 +0000
>         Arnab Roy <arniekol at gmail.com <mailto:arniekol at
gmail.com>> wrote:
> 
>             The systemd unit file looks like as follows:
> 
>             [Unit]
>             Description=Winbindd Service
>             After=syslog.target network.target
> 
>             [Service]
>             Environment=KRB5CCNAME=FILE:/run/samba/krb5cc_samba
>             Type=notify
>             NotifyAccess=all
>             PIDFile=/var/run/samba/
> 
> 
>         I know nothing about systemd, but, shouldn't there be something
like
>         'winbind.pid' on the end of the line above?
> 
> 
>     there should be no PIDFile line at all - the whole point of
>     Type=notify is a direct communication channel where a non-forking
>     main-pid tells systemd "i am ready to accept connections"

Thanks for this, looks like you have nailed it that was the root cause of
the problem!

Any ideas what is required to build with systemd support, I have installed
every systemd-devel package I could find ..?

On Thu, Nov 23, 2017 at 10:26 PM, Reindl Harald via samba <
samba at lists.samba.org> wrote:
>
>
> Am 23.11.2017 um 23:16 schrieb Arnab Roy:
>
>> No dice :( removed as suggested updated unit file looks like this
>>
>
> "Type=notify" can not work until systemd-support was successful
built
> which does not seem to be the case looking at the starting posts!
>
> [Unit]
>> Description=KKonnect KHIPU-NETWORKS Service
>> After=syslog.target network.target
>>
>> [Service]
>> Environment=KRB5CCNAME=FILE:/run/samba/krb5cc_samba
>> Type=notify
>> NotifyAccess=all
>> ExecStart=/usr/local/samba/sbin/winbindd
>> ExecReload=/usr/bin/kill -HUP $MAINPID
>> LimitCORE=infinity
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> I had lifted the unit file from an rpm install of samba from fedora.
>>
>> Thanks
>> Arnab
>>
>> On Thu, Nov 23, 2017 at 10:09 PM, Reindl Harald via samba <
>> samba at lists.samba.org <mailto:samba at lists.samba.org>>
wrote:
>>
>>
>>
>>     Am 23.11.2017 um 23:03 schrieb Rowland Penny via samba:
>>
>>         On Thu, 23 Nov 2017 21:46:17 +0000
>>         Arnab Roy <arniekol at gmail.com <mailto:arniekol at
gmail.com>> wrote:
>>
>>             The systemd unit file looks like as follows:
>>
>>             [Unit]
>>             Description=Winbindd Service
>>             After=syslog.target network.target
>>
>>             [Service]
>>             Environment=KRB5CCNAME=FILE:/run/samba/krb5cc_samba
>>             Type=notify
>>             NotifyAccess=all
>>             PIDFile=/var/run/samba/
>>
>>
>>         I know nothing about systemd, but, shouldn't there be
something
>> like
>>         'winbind.pid' on the end of the line above?
>>
>>
>>     there should be no PIDFile line at all - the whole point of
>>     Type=notify is a direct communication channel where a non-forking
>>     main-pid tells systemd "i am ready to accept connections"
>>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

Am 23.11.2017 um 23:36 schrieb Arnab Roy:
> Thanks for this, looks like you have nailed it that was the root cause 
> of the problem!
> 
> Any ideas what is required to build with systemd support, I have 
> installed every systemd-devel package I could find ..?
as said: for MariaDB on Fedora 25/26 you need only "systemd-devel" and
so this is is pretty clear samba related or caused by something in your 
./configure

focus on the build meaning post your whole configure / build stuff, i am 
out here because i don't build samba from source but it's clear that the
systemd support needs to be solved or you need to stick with
"Type=forking"
> On Thu, Nov 23, 2017 at 10:26 PM, Reindl Harald via samba 
> <samba at lists.samba.org <mailto:samba at lists.samba.org>>
wrote:
> 
>     Am 23.11.2017 um 23:16 schrieb Arnab Roy:
> 
>         No dice :( removed as suggested updated unit file looks like this
> 
> 
>     "Type=notify" can not work until systemd-support was
successful
>     built which does not seem to be the case looking at the starting posts!

Am 23.11.2017 um 23:51 schrieb Arnab Roy:
> Here you go...
> 
> Checking for program gcc or cc           : /usr/bin/gcc
and you think your ./configure command line don't matter or if you just 
type ./confugure without any params state so?

Checking for libsystemd-daemon 
                        : not found
Checking for libsystemd-journal 
                        : not found
Checking for libsystemd 
                        : not found
Checking for library systemd 
                        : no

however, that above looks like a samba bug whenyou have
"systemd-devel"
installed as oyu say

[root at buildserver:~]$ rpm -q --filesbypkg systemd-devel | grep libsystemd
systemd-devel             /usr/lib64/libsystemd.so
systemd-devel             /usr/lib64/pkgconfig/libsystemd.pc
> On Thu, Nov 23, 2017 at 10:40 PM, Reindl Harald via samba 
> <samba at lists.samba.org <mailto:samba at lists.samba.org>>
wrote:
> 
> 
> 
>     Am 23.11.2017 um 23:36 schrieb Arnab Roy:
> 
>         Thanks for this, looks like you have nailed it that was the root
>         cause of the problem!
> 
>         Any ideas what is required to build with systemd support, I have
>         installed every systemd-devel package I could find ..?
> 
> 
>     as said: for MariaDB on Fedora 25/26 you need only
"systemd-devel"
>     and so this is is pretty clear samba related or caused by something
>     in your ./configure
> 
>     focus on the build meaning post your whole configure / build stuff,
>     i am out here because i don't build samba from source but it's
clear
>     that the systemd support needs to be solved or you need to stick
>     with "Type=forking"
> 
>         On Thu, Nov 23, 2017 at 10:26 PM, Reindl Harald via samba
>         <samba at lists.samba.org <mailto:samba at
lists.samba.org>
>         <mailto:samba at lists.samba.org <mailto:samba at
lists.samba.org>>>
>         wrote:
> 
>              Am 23.11.2017 um 23:16 schrieb Arnab Roy:
> 
>                  No dice :( removed as suggested updated unit file looks
>         like this
> 
> 
>              "Type=notify" can not work until systemd-support was
successful
>              built which does not seem to be the case looking at the
>         starting posts!

On Thu, 23 Nov 2017 22:36:08 +0000
Arnab Roy via samba <samba at lists.samba.org> wrote:
> Thanks for this, looks like you have nailed it that was the root
> cause of the problem!
> 
> Any ideas what is required to build with systemd support, I have
> installed every systemd-devel package I could find ..?
> 
Have a look here:

https://wiki.samba.org/index.php/Package_Dependencies_Required_to_Build_Samba

If you just need everything to end up in /usr/local/samba , you can
just run './configure' , this should find everything.

Rowland