Commits on Jun 9, 2020

1. doc: Try to clarify automount dependency confusion …

   Arch recently upgraded systemd to 245.6. Shortly afterwards, users began
   reporting[0] that systemd detected an ordering cycle, and they were
   unable to log in. The reason they were unable to log in was because of
   ordering cycle resolution:
   
       [...]
       systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
       systemd[1]: sysinit.target: Job systemd-update-done.service/start deleted to break ordering cycle starting with sysinit.target/start
       systemd[1]: sysinit.target: Job systemd-journal-catalog-update.service/start deleted to break ordering cycle starting with sysinit.target/start
       systemd[1]: sysinit.target: Job local-fs.target/start deleted to break ordering cycle starting with sysinit.target/start
       systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
       [...]
   
   Whether the resolution did the right thing here or not is a longer-term
   discussion, but in the interim we should at least make this distinction
   between automount dependencies and mount dependencies clearer in the
   documentation, so that users and distribution maintainers know what's
   acceptable. In this case Arch actually backed out b3d7aef entirely and
   released a new version due to the confusion.
   
   Also see systemd/systemd-stable#69.
   
   0: https://bugs.archlinux.org/task/66908

   

   cdown committed Jun 9, 2020
   Copy the full SHA

   f0eaa3a View commit details

   Browse the repository at this point in the history