Control: tags -1 + moreinfo On Wed, 25 Nov 2020 09:54:35 +0100 Anton Lundin <gla...@acc.umu.se> wrote: > Package: nullmailer > Version: 1:2.2-3 > > I use FAI to install debian 10 machines, and some of them uses > nullmailer to ship mail to a central smarthost. > > > The generated postinst script in nullmailer has a section like: > # Automatically added by dh_installinit/12 > if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = > "abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then > # In case this system is running systemd, we need to ensure that all > # necessary tmpfiles (if any) are created before starting. > if [ -d /run/systemd/system ] ; then > systemd-tmpfiles --create nullmailer.conf >/dev/null || true > fi > fi > # End automatically added section > > > The problem with this is that fai doesn't use systemd during the > install, but it's used when the machine reboots into the new install. > > > That causes the /var/spool/nullmailer/trigger pipe to never be created > and nullmailer doesn't work.
Well, systemd-tmpfiles is (also) run during boot, so /var/spool/nullmailer/trigger will be created once you actually boot your system with systemd. Afaics, there is nothing to fix in debhelper or nullmailer.
signature.asc
Description: This is a digitally signed message part
