Differences

This shows you the differences between two versions of the page.

--- doc:appunti:linux:sa:postfix_courier_authdaemon_debian_12 [2024/02/26 09:53] – niccolo
+++ doc:appunti:linux:sa:postfix_courier_authdaemon_debian_12 [2024/02/26 10:13] (current) – [Moving the Courier Authdaemon socket into the Postfix chroot] niccolo
@@ Line 66: / Line 66: @@
 </code>
-To enable the bind mount at bootstrap we create a **systemd mount service** creating the file **/etc/systemd/system/var-spool-postfix-var-run-courier-authdaemon.mount** with the following content:
+To enable the bind mount at bootstrap we define a **systemd mount service** creating the file **/etc/systemd/system/var-spool-postfix-var-run-courier-authdaemon.mount** with the following content:
 <file>
@@ Line 72: / Line 72: @@
 Description=Mount Courier Authdaemon into Postfix chroot
 Wants=courier-authdaemon.service
-# The "Requires=" and "After=" dependencies may be too strong
-# and they can generate and ordering cycle problem.
-#Requires=courier-authdaemon.service
-#After=courier-authdaemon.service
 [Mount]
-What=/var/run/courier/authdaemon
+What=/run/courier/authdaemon
 Where=/var/spool/postfix/var/run/courier/authdaemon
 Type=bind
@@ Line 86: / Line 82: @@
 WantedBy=postfix.service
 </file>
+**NOTICE**: The weak dependency ''Wants=courier-authdaemon.service'' is preferable than the stronger ones ''Requires='' and ''After=''. In Debian 12 the strong dependencies cause a Systemd ordering cycle problem, see **[[systemd_tmpfiles_problem]]**.
 This is a **[[https://www.freedesktop.org/software/systemd/man/systemd.mount.html|systemd mount unit]]**, we need to reload the systemd daemon and enable that unit for the next reboot: