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 ${HOSTNAME}:400
PrivateTmp=yes
PrivateNetwork=yes
--------------------
But still ldapsearch not working with ${HOSTNAME}:401.
Some useful info
# systemctl status proxy-to-directory-400.service
â proxy-to-directory-400.service
Loaded: loaded (/usr/lib/systemd/system/proxy-to-directory-400.service;
static)
Active: active (running) since Thu 2014-07-17 09:37:36 EEST; 5min ago
Main PID: 32744 (systemd-socket-)
CGroup: /system.slice/proxy-to-directory-400.service
ââ32744 /usr/lib/systemd/systemd-socket-proxyd CLA-0:400
--
# ss -anp | egrep -wi "400|401|402|403|49502|haproxy"
tcp LISTEN 0 128 169.254.0.4:400 *:*
users:(("slapd",32743,7))
tcp LISTEN 0 128 :::401 :::*
users:(("systemd-socket-",32744,3),("systemd",1,26))
Any further help.
On Thu, Jul 17, 2014 at 12:53 AM, David Timothy Strauss <
[email protected]> wrote:
> On Wed, Jul 16, 2014 at 7:29 AM, Zbigniew Jędrzejewski-Szmek
> <[email protected]> wrote:
> > This won't work, since proxyd now cannot connect to port 400.
>
> There is now a way to make that work with JoinsNamespaceOf=
>
--
Suvendu Mitra
GSM - +358504821066
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
