diff options
| author | Alexey Lebedeff <[email protected]> | 2016-03-29 20:30:22 +0300 |
|---|---|---|
| committer | Alexey Lebedeff <[email protected]> | 2016-03-29 20:30:22 +0300 |
| commit | 16b921ad1c847ba0754adc10d2d45b17973dcd19 (patch) | |
| tree | 608a382247d87fd6ad92f3b48063148ab272c20d /.mailmap | |
| parent | 523e048754f5086a6cc4fd9a250e1b495fc5b9b8 (diff) | |
| download | otp-16b921ad1c847ba0754adc10d2d45b17973dcd19.tar.gz otp-16b921ad1c847ba0754adc10d2d45b17973dcd19.tar.bz2 otp-16b921ad1c847ba0754adc10d2d45b17973dcd19.zip | |
Don't send unasked for systemd notifications
Suppose we have some erlang system that uses systemd unit with
Type=notify - so this should send startup confirmation itself. But if
systemd-enabled epmd will be started as a first step of that system
startup, empd startup confirmation will be misinterpeted by systemd. And
our erlang service will be considered 'ready' to early. Also this will
interefere with systemd MAINPID detection: systemd will be monitoring
`epmd` process instead of `beam` one.
For example, rabbitmq works around this issue by starting epmd using
separate short-lived beam process, with NOTIFY_SOCKET environment
variable reset - only in this way we could be sure that epmd will not
interfere with rabbit startup sequence.
This patch disables indiscriminate confirmation sending, and does it
only when it was explicitly asked to do so.
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions