search for: libsystemd

Since systemd 209, all the functionalities of the former libsystemd-* (including libsystemd-journal) have been merged into a single libsystemd, with the former libraries left as compatibility ones. Thus, first look for libsystemd, and if not found try again with the libsystemd-journal as used before. --- configure.ac | 13 ++++++++++--- 1 file changed, 10 inserti...

On Tue, Jul 12, 2016 at 9:32 AM, Sonic <sonicsmith at gmail.com> wrote: > It appears that Samba does not check for > libsystemd (only libsystemd-daemon and libsystemd-journal) during the > config phase so unless one is running some ancient version of systemd > the "--with-systemd" configure option may be quite useless. Might be wrong on this, see the ../lib/util/wscript_configure script in the src. It looks...

...ng 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...

...Jul 12, 2016 at 8:11 AM, mathias dufresne <infractory at gmail.com> wrote: >> It looks to me that configure script can't find Centos 7 systemd >> installation files. Any idea of what I would have missed? > Same issues with Debian Jessie - nothing you missed. Apparently > libsystemd-daemon and libsystemd-journal are deprecated and merged > into a single libsystemd file (must have happened some time ago since > Debian has the change). It appears that Samba does not check for > libsystemd (only libsystemd-daemon and libsystemd-journal) during the > config phase so un...

2016-07-12 15:49 GMT+02:00 Sonic <sonicsmith at gmail.com>: > On Tue, Jul 12, 2016 at 9:32 AM, Sonic <sonicsmith at gmail.com> wrote: > > It appears that Samba does not check for > > libsystemd (only libsystemd-daemon and libsystemd-journal) during the > > config phase so unless one is running some ancient version of systemd > > the "--with-systemd" configure option may be quite useless. > > Might be wrong on this, see the ../lib/util/wscript_configure script &...

On Tue, Jul 12, 2016 at 8:11 AM, mathias dufresne <infractory at gmail.com> wrote: > It looks to me that configure script can't find Centos 7 systemd > installation files. Any idea of what I would have missed? Same issues with Debian Jessie - nothing you missed. Apparently libsystemd-daemon and libsystemd-journal are deprecated and merged into a single libsystemd file (must have happened some time ago since Debian has the change). It appears that Samba does not check for libsystemd (only libsystemd-daemon and libsystemd-journal) during the config phase so unless one is running...

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 "sys...

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

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] >

...path provided by systemd, as a sanity check. Support for this feature is > enabled by the --with-systemd configure flag. > > --- > Something tells me upstream would not be interested in this patch, but > as it may be useful on linux, I'm submitting it here. yeah - unfortunately libsystemd is under the LGPL and we've tried hard to keep our license free of additional obligations. -d

...a sanity check. Support for this feature is >> enabled by the --with-systemd configure flag. >> >> --- >> Something tells me upstream would not be interested in this patch, but >> as it may be useful on linux, I'm submitting it here. > > yeah - unfortunately libsystemd is under the LGPL and we've tried hard > to keep our license free of additional obligations. Would a version that reimplemented sd_listen_fds(3) be okay? sd_listen_fds(3) is just a convenience function. The actual protocol is independent of both libsystemd and of systemd itself. -- Sincer...

...> > > > I am unable to start samba from systemd , systemd kills the > process off > > > after startup. I have installed the systemd-devel as recommended, > I guess I > > > am missing more dependencies > > > > > > Checking for libsystemd-daemon > > > : not found > > > Checking for libsystemd-journal > > > : not found > > > Checking for libsystemd > > > : not found > > > Checking for library sys...

...) + fi + ] +) + use_stack_protector=1 use_toolchain_hardening=1 AC_ARG_WITH([stackprotect], @@ -3376,6 +3386,18 @@ AC_CHECK_LIB([crypt], [crypt], [ AC_CHECK_FUNCS([crypt]) LIBS="$saved_LIBS" +if test "x$systemd" == "xyes" ; then + # Check for sd_listen_fds in libsystemd for socket activation + saved_LIBS="$LIBS" + AC_CHECK_LIB([systemd], [sd_listen_fds], [ + LIBS="-lsystemd $LIBS" + AGENTLIBS="-lsystemd $AGENTLIBS" + ]) + AC_CHECK_FUNCS([sd_listen_fds]) + LIBS="$saved_LIBS" + AC_SUBST([AGENTLIBS]) +fi + # Check for PAM li...

On 04 Feb (10:46:55), Daniel Kahn Gillmor wrote: > On Thu 2016-02-04 07:40:39 -0500, David Goulet wrote: > > > I would like to know if adding support for Unix socket to sshd would be a > > feature that would be consider to be added upstream? (ListenAddress). > > fwiw, i think this is a good idea, but i wouldn't implement it as an > explicit ListenAddress option:

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 without very careful consideration. I've read through the debian and Red Hat bug reports. There a...

On 10/5/2020 11:58 AM, Rowland penny via samba wrote: > On 05/10/2020 16:30, Jason Keltz via samba wrote: >> Hi. >> >> Using MIT5 backend with Samba.. > I hope you mean on the clients, the use of MIT as the kdc on a Samba > DC is experimental and shouldn't be used in production Hi Roland, our environment uses CentOS 7.? I don't have much choice but to use this

...0 => /xsys/lib64/libgnutls.so.30 > (0x00007ff84f37c000) > ??????? libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007ff84f145000) > ??????? libdl.so.2 => /lib64/libdl.so.2 (0x00007ff84ef41000) > ??????? libiconv.so.2 => /xsys/lib64/libiconv.so.2 (0x00007ff84ec5b000) > ??????? libsystemd-journal.so.0 => /lib64/libsystemd-journal.so.0 > (0x00007ff84ea36000) > ??????? libsystemd-daemon.so.0 => /lib64/libsystemd-daemon.so.0 > (0x00007ff84e82f000) > ??????? libpopt.so.0 => /lib64/libpopt.so.0 (0x00007ff84e625000) > ??????? libpthread.so.0 => /lib64/libpthre...

Package: xen Severity: important User: bluca at debian.org Usertags: missing-systemd-service Dear Maintainer(s), xen has been flagged by Lintian as shipping a sysv-init script without a corresponding systemd unit file. The default init system in Debian is systemd, and so far this worked because a transitional sysv-init-to-unit generator was shipped by systemd. This is in the process of being

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

...it a/appliance/packagelist.in b/appliance/packagelist.in index f278f66..2da7533 100644 --- a/appliance/packagelist.in +++ b/appliance/packagelist.in @@ -51,6 +51,7 @@ ifelse(REDHAT,1, vim-minimal xz yajl + yara zfs-fuse ) @@ -83,6 +84,7 @@ dnl iproute has been renamed to iproute2 libsystemd-id128-0 libsystemd-journal0 libyajl2 + libyara3 linux-image dnl syslinux 'suggests' mtools, but in reality it's a hard dependency: mtools @@ -125,6 +127,7 @@ ifelse(ARCHLINUX,1, vim xz yajl + yara ) ifelse(SUSE,1, @@ -152,6 +155,7 @@ ifelse(SUSE,1, syste...