mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[PR #576] [MERGED] fix: execute systemctl daemon-reload after /etc/fstab changes #584
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#584
Loading…
Add table
Add a link
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?
📋 Pull Request Information
Original PR: https://github.com/ovh/the-bastion/pull/576
Author: @jon4hz
Created: 9/4/2025
Status: ✅ Merged
Merged: 9/5/2025
Merged by: @speed47
Base:
master← Head:fix-encrypt-systemd-reload📝 Commits (1)
a75f88bfix: execute systemctl daemon-reload after /etc/fstab changes📊 Changes
1 file changed (+8 additions, -0 deletions)
View changed files
📝
bin/admin/setup-encryption.sh(+8 -0)📄 Description
Hi,
Most servers using systemd require a
sytemctl daemon-reloadafter making changes to/etc/fstabbecause systemd generates systemd-mounts for all mount points under the hood.Without the daemon-reload, I'm getting this warning:
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.