systemd notify protocol #552
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#552
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Support systemd notify protocol using systemdNotifyMsg in all services and use
notify
type in systemd units instead ofsimple
. This will communicate the real service status to systemd and improve dependent service handling.It is a simple message on a unix socket, I suggest not using any external dependencies for this (though consider having
TrueCloudLab/sdnotify
).We should also continue to work in non-systemd environments without hassles.
Sure. May be done like
7565e5c3de
STOPPING
#1283