highperfocused/lnd
1
0
Fork 0
mirror of https://github.com/lightningnetwork/lnd.git synced 2025-07-13 22:52:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

signal: clarify the log message about systemd

Browse Source 
The log message was confusing because it was emitted even when running
within systemd if the service type was **not** `notify`. This clarifies
the message by mentioning the edge case.

Being able to distinguish the two cases would be nicer but there doesn't
seem to be a reasonably simple, obvious, reliable way to do it.
Complicated solutions are most likely not worth it for a simple log
message.
This commit is contained in:
Martin Habovstiak
2021-12-16 13:23:53 +01:00
parent 3e57d1d416
commit 17cf90ee34
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/release-notes/release-notes-0.14.2.md
View File

@ -42,6 +42,9 @@
* [Ensure that the min relay fee is always clamped by our fee * [Ensure that the min relay fee is always clamped by our fee
floor](https://github.com/lightningnetwork/lnd/pull/6076) floor](https://github.com/lightningnetwork/lnd/pull/6076)
* [Clarify log message about not running within
systemd](https://github.com/lightningnetwork/lnd/pull/6096)
## RPC Server ## RPC Server
* [ChanStatusFlags is now * [ChanStatusFlags is now

3
signal/signal.go
View File

@ -42,7 +42,8 @@ func systemdNotifyReady() error {
if notified { if notified {
log.Info("Systemd was notified about our readiness") log.Info("Systemd was notified about our readiness")
} else { } else {
log.Info("We're not running within systemd") log.Info("We're not running within systemd or the service " +
"type is not 'notify'")
} }
return nil return nil
} }