Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@YHNdnzj
Copy link
Member

@YHNdnzj YHNdnzj commented Nov 16, 2025

No description provided.

Up until now there's no sane way for notify-reload services to
report failure to service manager. While we encourage handling
such failure gracefully in the main process, the reload job
should almost certainly fail. Hence, let's introduce a way
for service to communicate the fact.

RELOADING=-1 is expected to be sent alongside either READY=1
or STOPPING=1, for gracefully handled errors and fatal ones,
respectively. This also ensures older service manager properly
behaves without support for the message.
…_dbus

No functional change, preparation for later commits. This also
makes the logic consistent with varlink call.
@YHNdnzj YHNdnzj force-pushed the reload-report-error branch 2 times, most recently from c5c4602 to 506b489 Compare November 16, 2025 01:38
With the previous commit, Manager.pending_reload_message_* won't be
lingering around if reload fails. IOW, they are set iff MANAGER_IS_RELOADING
or send_reloading_done is true.
@YHNdnzj YHNdnzj force-pushed the reload-report-error branch from 506b489 to 25b266f Compare November 16, 2025 01:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant