[systemd-devel] Clarification on notify-reload and SIGHUP handling

[Łukasz Niemier]

I am working on Erlang-native implementation of libsystemd-like interface (for the integration layer only). And right now I started working on integrating `notify-reload`, but I have encountered an issue. When I am running `systemctl reload echo` with my integration then I see weird behaviour:
- SIGHUP is received
- `RELOADING=1` message is sent
- after five seconds I send `READY=1` message

However systemd is still reporting that the service is reloading. This behaviour do not occur when I try to run `kill -HUP <pid>` or when I manually send both messages from the process.

I cannot find where is problem, is there any special case that I need to take care of?

$ systemctl --version
systemd 256 (256.5-2ubuntu3.1)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE

--

Łukasz Niemier
lukasz at niemier.pl