5 Commits

Author	SHA1	Message	Date
Naïm Favier	2ddc335e6f	nixos/doc: clean up defaults and examples	2021-10-04 12:47:20 +02:00
happysalada	d874a52015	epmd: provide default	2021-08-30 22:26:57 +09:00
happysalada	8a56ac5db3	epmd: add ipv6 assertion	2021-08-30 19:51:00 +09:00
Eric Bailey	35056b3b61	maintainers/teams: add beam team	2021-02-07 13:01:11 -06:00
Alexey Lebedeff	c00d17aae3	epmd: Introduce erlang port mapper daemon service ... Having socket-activated epmd means that there always be only a single instance managed centrally. Because Erlang also starts it automatically if not available, and in worst case scenario 'epmd' can be started by some Erlang application running under systemd. And then restarting this application unit will cause complete loss of names in 'epmd' (if other Erlang system are also installed on this host). E.g. see at which lengths RabbitMQ goes to recover from such situations: 7741b37b1e/src/rabbit_epmd_monitor.erl (L36) Having the only one socket-activated epmd completely solves this problem.	2018-07-19 17:32:29 +02:00