man: add self-contained example of notify protocol

[thirdparty/systemd.git] / docs / ROOT_STORAGE_DAEMONS.md

diff --git a/docs/ROOT_STORAGE_DAEMONS.md b/docs/ROOT_STORAGE_DAEMONS.md
index 86aefe105739ee9db740ef5d7f184b72838401d9..69812c905591e0b49132857c151a124f2aaeb00b 100644 (file)
--- a/docs/ROOT_STORAGE_DAEMONS.md
+++ b/docs/ROOT_STORAGE_DAEMONS.md
@@ -106,7 +106,7 @@ to find a different solution to your problem._
 
 The recommended way to distinguish between run-from-initrd and run-from-rootfs
 for a daemon is to check for `/etc/initrd-release` (which exists on all modern
-initrd implementations, see the [initrd Interface](INITRD_INTERFACE.md) for
+initrd implementations, see the [initrd Interface](INITRD_INTERFACE) for
 details) which when exists results in `argv[0][0]` being set to `@`, and
 otherwise doesn't. Something like this:
 
@@ -137,6 +137,9 @@ is a cool character which looks pretty in the ps output... 😎
 Note that your code should only modify `argv[0][0]` and leave the comm name
 (i.e. `/proc/self/comm`) of your process untouched.
 
+Since systemd v255, alternatively the `SurviveFinalKillSignal=yes` unit option
+can be set, and provides the equivalent functionality to modifying `argv[0][0]`.
+
 ## To which technologies does this apply?
 
 These recommendations apply to those storage daemons which need to stay around
@@ -188,4 +191,4 @@ few additional notes for supporting these setups:
   program consult this blog story: [Socket
   Activation](https://0pointer.de/blog/projects/socket-activation.html)
 
-* Consider having a look at the [initrd Interface of systemd](INITRD_INTERFACE.md).
+* Consider having a look at the [initrd Interface of systemd](INITRD_INTERFACE).