Would you be willing to post the entire unit files for everything
here, just so future users can see them? Presumably, you're using
JoinsNamespaceOf=proxy-to-directory-400.service in
vgp.master-ldap-400.service?
___
systemd-devel mailing list
systemd-deve
On Wed, Jul 23, 2014 at 11:13:50AM +0300, Suvendu Mitra wrote:
> Thanks now it works, But does it mandatory to start slapd on same port as
> "ListenStream=" of socket file of systemd-socket-proxyd. e.g in following
> example port 400.
Maybe the protocol embeds the port number in the stream? That wo
Thanks now it works, But does it mandatory to start slapd on same port as
"ListenStream=" of socket file of systemd-socket-proxyd. e.g in following
example port 400.
# cat proxy-to-directory-400.service
[Unit]
Requires=master-ldap-400.service
After=master-ldap-400.service
[Service]
ExecStart=/usr
On Thu, Jul 17, 2014 at 4:51 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> I'd try without Private* settings.
>
> Also, replace /usr/lib/systemd/systemd-socket-proxyd with
> '/bin/strace -o /tmp/log /usr/lib/systemd/systemd-socket-proxyd'
> and look at the log file.
Yes, get it working without Private
On Thu, Jul 17, 2014 at 09:43:48AM +0300, Suvendu Mitra wrote:
> I have changed proxy-to-directory-400.service as
>
> # cat proxy-to-directory-400.service
> [Unit]
> Requires=vgp.master-ldap-400.service
> After=vgp.master-ldap-400.service
> JoinsNamespaceOf=vgp.master-ldap-400
I have changed proxy-to-directory-400.service as
# cat proxy-to-directory-400.service
[Unit]
Requires=vgp.master-ldap-400.service
After=vgp.master-ldap-400.service
JoinsNamespaceOf=vgp.master-ldap-400.service
[Service]
ExecStart=/usr/lib/systemd/systemd-socket-proxyd ${HOSTNA
On Wed, Jul 16, 2014 at 7:29 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> This won't work, since proxyd now cannot connect to port 400.
There is now a way to make that work with JoinsNamespaceOf=
___
systemd-devel mailing list
systemd-devel@lists.freedeskto
On Wed, Jul 16, 2014 at 03:45:53PM +0300, Suvendu Mitra wrote:
> want to start slapd with socket activation via 'systemd-socket-proxyd' ,
>
> I can see that slapd is listening to port 400 & sytemd create socket at
> 401. But ldapsearch doesn't work with port 401. Any help !!
>
>
want to start slapd with socket activation via 'systemd-socket-proxyd' ,
I can see that slapd is listening to port 400 & sytemd create socket at
401. But ldapsearch doesn't work with port 401. Any help !!
---
1.
$ cat proxy-to-directory-400.socket
[Socket]
ListenStream=401
[Inst
