Enable the reloading of systemd credentials #1495
Labels
No labels
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!1495
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Kimiblock/continuwuity:main"
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?
systemd v260 has introduced a new option: RefreshOnReload, of which when set to true automatically reloads all confext and credential files. This should eliminate the full restart requirement to reload a changed configuration.
Older systems should just see an unknown option warning and does not fail outright.
Man page here:
github.com/systemd/systemd@240675efeb/man/systemd.service.xml (L1374)lgtm assuming the credential reload happens before the signal is sent to c10y
Yeah we'll see when 260 lands
93e7cb00c885cb92d636we may as well fix the other thing systemd complains about in my logs:
I think
StartLimitBurstandStartLimitIntervalare also misplaced and one of them is deprecated, but I don't know the exact versions these changes occurred nor our guaranteed SLA range.Indeed we can start dropping Alias since it’s long since the migration