core-lightning/tests/plugins/badopeningd.sh

#! /bin/sh

# If this file exists, we send that message back, then sleep.
if [ "$1" != "--version" ] && [ -f openingd-version ]; then
    # lightningd expects us to write to stdin!
    cat openingd-version >&0
    sleep 10
    exit 0
fi

exec "$(cat openingd-real)" "$@"
lightningd: don't abort on incorrect versions, but try to re-exec. You still shouldn't do this (you could get some transient failures), but at least you have a decent chance if you reinstall over a running daemon, instead of getting confusing internal errors if message formats have changed. Changelog-Added: lightningd: we now try to restart if subdaemons are upgraded underneath us. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Fixes: #4346 2021-04-16 14:01:24 +09:30			`#! /bin/sh`

			`# If this file exists, we send that message back, then sleep.`
lightningd: pass --developer down to plugins, subdaemons when it set. They might need to know this before they do anything, so cmdline seems most natural. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2023-09-21 15:06:26 +09:30			`if [ "$1" != "--version" ] && [ -f openingd-version ]; then`
lightningd: don't abort on incorrect versions, but try to re-exec. You still shouldn't do this (you could get some transient failures), but at least you have a decent chance if you reinstall over a running daemon, instead of getting confusing internal errors if message formats have changed. Changelog-Added: lightningd: we now try to restart if subdaemons are upgraded underneath us. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Fixes: #4346 2021-04-16 14:01:24 +09:30			`# lightningd expects us to write to stdin!`
			`cat openingd-version >&0`
			`sleep 10`
			`exit 0`
			`fi`

			`exec "$(cat openingd-real)" "$@"`