After editing the ExecStart line of a custom unit file stored in /etc/systemd/system/myapp.service, an administrator runs systemctl restart myapp.service, but the service still starts the old binary. Which single command must be executed first so that systemd recognizes the modified unit file without requiring a reboot?
When a unit file is added or altered on disk, systemd continues to use the version that is already loaded in memory until it is explicitly told to reread the unit database. The systemctl daemon-reload command forces the systemd manager to scan all unit files again and rebuild its dependency tree. After this reload, a subsequent systemctl restart (or start) uses the updated directives. The other commands do not reload changed unit definitions: reset-failed only clears the failed state, disable removes enablement symlinks, and unmask removes a /dev/null symlink that blocks activation but does not refresh cached metadata.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What does 'systemctl daemon-reload' do?
Open an interactive chat with Bash
Why does systemd cache unit files?
Open an interactive chat with Bash
What is the difference between 'systemctl restart' and 'systemctl daemon-reload'?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Services and User Management
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access