similar to: [Bug 2641] New: Add systemd notify code to to track running server

On Wed, 2018-08-22 at 09:02 -0500, kevin martin wrote: > Simple seems to have fixed it. I was also trying with "forking" as > the > type and that was failing as well. That is not as simple as that -- we lived with "simple" for long time, but it was not covering some corner cases so we ended up using the sd_notify, since that was the only reliable way for systemd to

> I don't know much about the > D-bus protocol, but if a small D-bus client is just opening a unix > domain > socket and writing a message to it then we could possibly support it > using a standalone implementation, like we just did for systemd. Afraid not, D-Bus is a stateful protocol with client authentication and so much more, it's not something you really want to

On Wed, Aug 22, 2018 at 11:23:11AM +0000, Peter Stuge wrote: > I guess that Oracle has patched sshd to call sd_notify() and thus Well, RedHat. > introduced dependency on the systemd libraries for sshd. I don't Yup % ldd /usr/sbin/sshd | grep syst libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007f0e5b715000) -- rgds Stephen

https://bugzilla.mindrot.org/show_bug.cgi?id=3558 Bug ID: 3558 Summary: Spelling "yes" as "Yes" in sshd_config has a fatal result Product: Portable OpenSSH Version: 7.2p2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

kevin martin wrote: > not sure why having the systemd notify code in openssh as a > configure time option would be such a bad thing. At the very least it introduces a dependency on libsystemd into sshd, which is undesirable for reasons of security and convenience. The principle of "you are done when you can not remove any more" confirms that it is unwise to add dependencies

Damien Miller wrote: > I agree: what is happening here seems to be mostly bad assumptions and > inflexibility inside systemd. I didn't say that, and I don't agree with that, to me it's welcome ambition rather than bad assumptions. Consider this: How could systemd determine whether startup of a foreground daemon completed successfully or failed? Other than explicit

Hello, If I make a change to the smb.conf file. Can I simply invoke 'smbcontrol all reload-config', or must I kill all samba services and restart them? -- -James

Latest Oracle Linux (7.5) and openssh 7.4 is bundled as an rpm. this runs fine. if I download openssh 7.6 or 7.7, compile it with the flags --with-pam and --with-pid-dir=/var/run and install it to /usr/local, modify the sshd.service file to point to /usr/local/sbin/sshd, the start hangs. The sshd.service files looks like this: [Unit] Description=OpenSSH server daemon Documentation=man:sshd(8)

Hi: The openssh suite of commands have an option to specify address (e.g, ListenAddress for sshd) but I do not see support for bind-to-interface. The motivating use case for me is using openssh commands (sshd, ssh, scp, sftp) with the recent VRF capability added to the Linux kernel. The VRF design relies on the bind-to-interface option to select the correct routing tables. Before I started

Hi, Am rebuilding httpd from scratch to enable http2 and minimize extra modules on Cent Os 8. Am having trouble understanding the spec file [0] and systemd initialization [1][2][3] (these are very similar to those extracted from [4]). Why are 3 scripts needed to start the service and why is a pid setting not needed as used in the httpd.service file at [5]? Benson [0]

Hello. The problem with dovecot/config processes never ending and spawning new one on each reload (https://www.dovecot.org/list/dovecot/2016-November/106058.html) is becoming a problem here: # ps aux|grep dovecot/config|wc -l 206 That's a lot of wasted memory - dovecot/config processes ate over 30GB of ram on 64GB box. Before killing dovecot/config processes: # free -m total

> On Wed, Jan 09, 2019 at 10:43:38AM -0500, Steve Clark wrote: >> I am trying to understand what After= means in a unit file. Does it >> mean after the specified target is up and operational or only that >> the target has been started? >> >> I have something that needs postgres but postgres needs to be >> operational not just started. Sometimes it can take a

On Thu, 21 Jun 2018 19:17:14 +0700 Vladimir Eltsov via samba <samba at lists.samba.org> wrote: > Hello. > > I have read man smbcontrol. > > I wrote in start message: > > > I have tried: > > systemctl reload smbd.service > > killall -1 smbd > > pkill -HUP smbd Forget 'systemctl reload' Forget 'killall' Forget 'pkill' >

Hi everybody, I've set up an new CentOS 7.6.1810 server. Then, via yum I installed qemu-kvm libvirt libvirt-python libguestfs-tools virt-install. There were no problems. But when I try to systemctl start libvirtd I get the following message: "libvirtd: process 472: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)"

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/ ExecStart=/usr/local/samba/sbin/winbindd -D ExecReload=/usr/bin/kill -HUP $MAINPID LimitCORE=infinity [Install] @Rowland I am not blaming samba at all, certainly is

On 6/19/23 20:20, Damien Miller wrote: > > On Fri, 16 Jun 2023, Ronan Pigott wrote: > >> This adds support for systemd socket-based activation in the ssh-agent. >> When using socket activation, the -a flag value must match the socket >> path provided by systemd, as a sanity check. Support for this feature is >> enabled by the --with-systemd configure flag.

I'm having trouble changing the machine name programmatically on Samba 4 (running under systemd). There's no "netbios name" option in smb.conf, so I'm relying on it using the hostname. Here's what I'm doing: 1) Call sethostname() with the new name. 2) Write the same name into /etc/hostname, to make it nonvolatile. 3) Read a decimal number from /var/run/smbd.pid.

running 2.05a on red hat 6.1 I get a lot of these in my logs: smbd/process.c:timeout_processing(868) Reloading services after SIGHUP. Can anyone shed any light on this?

https://bugzilla.mindrot.org/show_bug.cgi?id=1692 Summary: sshd sometimes dies when sent multiple SIGHUPs in quick succession Product: Portable OpenSSH Version: 5.3p1 Platform: Other URL: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug /497781 OS/Version: Linux Status: NEW

Anybody else seen this one? We're running Dovecot 1.0.rc7 on a different port on our live server (we're generally live with 1.0.beta5) and after a HUP to reload the user database (in a passwd-file) this morning we got:- > dovecot: Sep 22 07:45:05 Info: IMAP 14482 someuser xxx.xxx.xxx.xxx : Disconnected in IDLE > dovecot: Sep 22 07:45:05 Warning: imap-login: SSL_read() syscall