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 09/07/16 16:56, Reindl Harald wrote:> > > 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-unitYou have your opinion and I have mine and my opinion (for what it is worth) is that systemd is something that is looking for a problem that doesn't really exist and then fixing the problem in a totally insane way. If systemd was just another init system and was easy to change then I wouldn't mind, but it keeps gobbling up things that have nothing to do with an init system and is becoming extremely hard to remove. As far as I am concerned, this ends this conversation, you have my opinion and nothing will change it, so don't bother trying. Rowland
Hello! Thanks for the information , I ask myself this question , why use Samba 4 with system Systemd , but have not used this option and at first it's all ok , I was in doubt with her on, would have some benefit . Thank you Em 09-07-2016 13:10, Rowland penny escreveu:> On 09/07/16 16:56, Reindl Harald wrote: >> >> >> 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 > > You have your opinion and I have mine and my opinion (for what it is > worth) is that systemd is something that is looking for a problem that > doesn't really exist and then fixing the problem in a totally insane > way. If systemd was just another init system and was easy to change > then I wouldn't mind, but it keeps gobbling up things that have > nothing to do with an init system and is becoming extremely hard to > remove. > > As far as I am concerned, this ends this conversation, you have my > opinion and nothing will change it, so don't bother trying. > > Rowland > > >
On Sat, Jul 9, 2016 at 11:56 AM, Reindl Harald <h.reindl at thelounge.net> wrote:> > > 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-unitExcept the horrible systemd logging, instead of flat text rsyslog, and the extraordinary difficulty of starting any of the daemons inside a usable debugger.> 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 optionsI agree that the shell scripts have often been frighteningly bad for many daemons. The problem has been solved with many, much lighter weight and safer init processes, and it integration for Samba makes Samba development less cross-platform compatible, since systemd *only* runs on Linux and cannot be integrated to other operating systems due to its kernel dependencies. My personal favorite has become daemontools, for which I publish SRPM's, but I don't see that replacing SysV init or systemd despite its gracefulness, stability, and maturity. Systemd has some useful features, especially logging boot-time kernel operations, but it still has *enormous* procedural and architectural problems. Binary logging instead of long-established plain text syslog style logs, unclear and unintuitive layout, insistent restarting of failed daemons, and the resulting overwriting of crash dumps from failed daemons as a result are all issues. The replacement of /etc/resolv.conf with an unstable symlink into its internal DHCP server, with no feature or plan to have a feature to reset the symlink if broken by accidenal user test editing with or manipulation by a configuraiton management system add to the destabilization and directly impinges Samba based DNS. Do not get me *started* on the recent systemd default "UserKillProcess" setting that terminates, silently and with no log whastoever any dangling user process that belongs to a user whose shell session has anded. This breaks screen, tmux, nohup'ed or otherwise backgrounded processes, including long-running hand-starteed Samba backups or database repair processes for which the active tty has ended. It's *nasty*.
Am 10.07.2016 um 03:34 schrieb Nico Kadel-Garcia:> On Sat, Jul 9, 2016 at 11:56 AM, Reindl Harald <h.reindl at thelounge.net> wrote: > I agree that the shell scripts have often been frighteningly bad for > many daemons. The problem has been solved with many, much lighter > weight and safer init processes, and it integration for Samba makes > Samba development less cross-platform compatible, since systemd *only* > runs on Linux and cannot be integrated to other operating systems due > to its kernel dependencies.how does that make development less cross-platform compatible? sorry but that is nonsense since you have to take care of special handling on other unix types too or just hope that it works there when no testing machines are available (see recent AIX topics and that nobody knows by lack of testing machines) integration with systemd watchdogs is just anotehr small piece of code to make monitoring relieable in case a service didn't crash but no longer works and makes things less complx since you can replace additional monitoring tools> My personal favorite has become > daemontools, for which I publish SRPM's, but I don't see that > replacing SysV init or systemd despite its gracefulness, stability, > and maturity.daemontools is a workaround for a broken init system which has no concept of what happend after fire up a service> Systemd has some useful features, especially logging boot-time kernel > operations, but it still has *enormous* procedural and architectural > problems. Binary logging instead of long-established plain text syslog > style logsa complete non-issue since journald (the part which takes care of early boot logging) don't need to wrote logs to disk as i does not on any of my machines which all use the rsyslog $WorkDirectory /var/lib/rsyslog $IMJournalStateFile imjournal.state> unclear and unintuitive layoutwrong, you just refuse to trying to understand it for many years> insistent restarting of failed daemons, and the resulting overwriting > of crash dumps from failed daemons as a result are all issuesnonsense - besides that it's not default this are your friends StartLimitIntervalSecStartLimitBurstStartLimitAction> The replacement of > /etc/resolv.conf with an unstable symlink into its internal DHCP > server, with no feature or plan to have a feature to reset the symlink > if broken by accidenal user test editing with or manipulation by a > configuraiton management system add to the destabilization and > directly impinges Samba based DNS.nonsense - that parts are completly optional to use> Do not get me *started* on the recent systemd default > "UserKillProcess" setting that terminates, silently and with no log > whastoever any dangling user process that belongs to a user whose > shell session has anded. This breaks screen, tmux, nohup'ed or > otherwise backgrounded processes, including long-running hand-starteed > Samba backups or database repair processes for which the active tty > has ended. It's *nasty*to make it short - i often don't agree with systemd developers, also in this case but when a default *option* where adjust it to your needs takes less to write than your whole paragraph about it i can't take it serious -------------- 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/20160710/bcb12acc/signature.sig>