il faut que je me fasse au workflow "Branch updater"

aws community guide

Keepalive Notes

A keepalive packet generally has a TCP ACK configured with a sequence number set to one less than the current number used on the connection. Any machine receiving a nudge from such a packet will simply respond with the correct sequence number and, Frankenstein jokes aside, announce that it is indeed alive.

These types of packets are sometimes empty and generally have three associated parameters. The retry parameter will declare how many times to send a packet before coming to the conclusion that the other end of the connection has given up the ghost. The time setting is configured as the frequency of the checks, and finally the interval dictates the length of time between two sent packets if no response is received.

Inside the kernel, you can alter these settings by editing these values in the eye-watering pseudo-filesystem known and loved as /proc. One file, in this case, is /proc/sys/net/ipv4/tcp_keepalive_time, and you can edit it

man systemd.index

You need ldapsearch from mozldap-tools (the classic ldapsearch does not have such options)

How I did :
docker run -it centos bash
yum install wget svrcore-devel.x86_64
wget ftp://195.220.108.108/linux/mageia/distrib/5/x86_64/media/core/release/mozldap-6.0.7-8.mga5.x86_64.rpm
wget ftp://bo.mirror.garr.it/1/mageia/distrib/5/x86_64/media/core/release/mozldap-tools-6.0.7-8.mga5.x86_64.rpm
rpm -ivh mozldap-6.0.7-8.mga5.x86_64.rpm
rpm -ivh mozldap-tools-6.0.7-8.mga5.x86_64.rpm

/usr/lib64/mozldap/ldapsearch -r -C PS:any:1:1 -D "cn=Admin Account" -w "secret" -p 9389 -h ldap.company.org -b dc=sso,dc=company,dc=org -s sub "(mail=toto*)"

Once the connection is established, you will receive notification on this one when a change is done

un peu homemade, mais why not

Note: Environment persistence can cause unexpected side effects. For example, setting ENV DEBIAN_FRONTEND noninteractive may confuse apt-get users on a Debian-based image. To set a value for a single command, use RUN <key>=<value> <command>.

The environment variables set using ENV will persist when a container is run from the resulting image. You can view the values using docker inspect, and change them using docker run --env <key>=<value>.

TIL pourquoi certains claviers ont une touche Enter différente :D