Advertisement
Guest User

Untitled

a guest
Sep 25th, 2017
55
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.28 KB | None | 0 0
  1. daemon-reload
  2. Reload systemd manager configuration. This will rerun all generators (see systemd.generator(7)), reload
  3. all unit files, and recreate the entire dependency tree. While the daemon is being reloaded, all sockets
  4. systemd listens on behalf of user configuration will stay accessible.
  5.  
  6. This command should not be confused with the reload command.
  7.  
  8. Generators are loaded from a set of paths determined during compilation, listed above. System and user
  9. generators are loaded from directories with names ending in system-generators/ and user-generators/,
  10. respectively. Generators found in directories listed earlier override the ones with the same name in
  11. directories lower in the list. A symlink to /dev/null or an empty file can be used to mask a generator,
  12. thereby preventing it from running. Please note that the order of the two directories with the highest
  13. priority is reversed with respect to the unit load path and generators in /run overwrite those in /etc.
  14.  
  15. After installing new generators or updating the configuration, systemctl daemon-reload may be executed. This
  16. will delete the previous configuration created by generators, re-run all generators, and cause systemd to
  17. reload units from disk. See systemctl(1) for more information.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement