Hello, Am 09.07.2016 um 09:14 schrieb Rowland penny:>> What is the purpose of the option >> * >> **--with-**systemd** >> ****Enable****systemd****integration* >> >> To configure Samba (build). >> > > It is there so that there is also the '--without-systemd' option. > > one turns on systemd integration, the other (thank your deity) turns it > off. > The second is more important, I think you get the systemd integration > without explicitly setting '--with-systemd'Carlos, it's a good question. I really never recognized this option. What is different afterwards when using with/without? Does it create a systemd service file? Regards, Marc
On 09/07/16 10:27, Marc Muehlfeld wrote:> Hello, > > Am 09.07.2016 um 09:14 schrieb Rowland penny: >>> What is the purpose of the option >>> * >>> **--with-**systemd** >>> ****Enable****systemd****integration* >>> >>> To configure Samba (build). >>> >> It is there so that there is also the '--without-systemd' option. >> >> one turns on systemd integration, the other (thank your deity) turns it >> off. >> The second is more important, I think you get the systemd integration >> without explicitly setting '--with-systemd' > > Carlos, it's a good question. I really never recognized this option. > > What is different afterwards when using with/without? Does it create a > systemd service file? > > > > Regards, > MarcDo not know about '--with-systemd', but there are no (horrible) systemd components if you use '--without-systemd' Rowland
Am 09.07.2016 um 17:19 schrieb Rowland penny:> On 09/07/16 10:27, Marc Muehlfeld wrote: >> What is different afterwards when using with/without? Does it create a >> systemd service file? >> > Do not know about '--with-systemd', but there are no (horrible) systemd > components if you use '--without-systemd'there is nothing horrible in a systemd service-unit horrible are large and complex shell scripts trying to do all sort of magic for start a service and with no clue about service states, no proper restart-otpions and no proper security options [root at srv-rhsoft:~]$ cat /etc/systemd/system/smb.service [Unit] Description=Samba SMB Daemon [Service] Type=forking LimitNOFILE=32768 ExecStart=/usr/sbin/smbd -D ExecReload=/usr/bin/kill -HUP $MAINPID Restart=always RestartSec=1 Nice=19 PrivateTmp=yes PrivateDevices=yes CapabilityBoundingSet=CAP_CHOWN CAP_SETGID CAP_SETUID CAP_DAC_OVERRIDE CAP_KILL CAP_NET_BIND_SERVICE CAP_IPC_LOCK CAP_SYS_CHROOT SystemCallFilter=~acct modify_ldt add_key adjtimex clock_adjtime delete_module fanotify_init finit_module get_mempolicy init_module io_destroy io_getevents iopl ioperm io_setup io_submit io_cancel kcmp kexec_load keyctl lookup_dcookie mbind migrate_pages mount move_pages open_by_handle_at perf_event_open pivot_root process_vm_readv process_vm_writev ptrace remap_file_pages request_key set_mempolicy swapoff swapon umount2 uselib vmsplice ReadOnlyDirectories=/etc ReadOnlyDirectories=/usr ReadOnlyDirectories=/var/lib ReadWriteDirectories=/var/lib/samba -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20160709/88bd9397/signature.sig>
On Sat, 2016-07-09 at 11:27 +0200, Marc Muehlfeld wrote:> Hello, > > Am 09.07.2016 um 09:14 schrieb Rowland penny: > > > What is the purpose of the option > > > * > > > **--with-**systemd** > > > ****Enable****systemd****integration* > > > > > > To configure Samba (build). > > > > > > > It is there so that there is also the '--without-systemd' option. > > > > one turns on systemd integration, the other (thank your deity) > > turns it > > off. > > The second is more important, I think you get the systemd > > integration > > without explicitly setting '--with-systemd' > > > Carlos, it's a good question. I really never recognized this option. > > What is different afterwards when using with/without? Does it create > a > systemd service file?It just means we link to a small library that helps systemd know that we started up successfully, as I understand it. This is needed because of the way we double-fork() at startup, so the original PID values from the process that called exec() is not the long -term PID. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
2016-07-10 2:12 GMT+02:00 Andrew Bartlett <abartlet at samba.org>:> On Sat, 2016-07-09 at 11:27 +0200, Marc Muehlfeld wrote: > > Hello, > > > > Am 09.07.2016 um 09:14 schrieb Rowland penny: > > > > What is the purpose of the option > > > > * > > > > **--with-**systemd** > > > > ****Enable****systemd****integration* > > > > > > > > To configure Samba (build). > > > > > > > > > [removed troll]> > Carlos, it's a good question. I really never recognized this option. > > > > What is different afterwards when using with/without? Does it create > > a > > systemd service file? > > It just means we link to a small library that helps systemd know that > we started up successfully, as I understand it. > > This is needed because of the way we double-fork() at startup, so the > original PID values from the process that called exec() is not the long > -term PID. >Andrew, I expect the --with-systemd is to add the little piece of code which makes Samba systemd unit files to work correctly, for systemd stop killing processes after some timeout because it doesn't received the right message from Samba. I ask because we are using last Samba and systemd (in version 219 today on Centos7), we are using shipped systemd unit files (or at least I expect that's Samba which create them, not the .spec / rpmbuild tool) and service samba-ad works well when samba-smbd, samba-nmdb and samba-winbindd are all three killed by systemd after timeout. Of course Samba works well, running these daemons just calling their names is sufficient for the service starts well. I did add --with-systemd to our .spec, compiled a 4.4.5, tested it as file server and same issue: systemd refuses to understand these processes are working and kill after some time. Checking logs of that compilation I get: ... Checking for libsystemd-daemon : not found Checking for library systemd-daemon : no Checking for library systemd-libs : no Checking for libsystemd-journal : not found Checking for library systemd-journal : no Checking for library systemd : no ... when rpm -qa systemd* systemd-libs-219-19.el7_2.9.x86_64 systemd-219-19.el7_2.9.x86_64 systemd-sysv-219-19.el7_2.9.x86_64 systemd-python-219-19.el7_2.9.x86_64 It looks to me that configure script can't find Centos 7 systemd installation files. Any idea of what I would have missed? Cheers, mathias