Control: tag -1 + confirmed pending 28.01.2025 23:29, Andreas Hasenack wrote: ...
This leads to rsyslogd throwing this error in the logs: 2025-01-28T20:26:13.670487+00:00 sid rsyslogd: cannot create '/var/spool/postfix/dev/log': No such file or directory [v8.2412.0 try https://www.rsyslog.com/e/2176 ]
Yes, as you found out later, I stopped shipping /var/spool/postfix/dev dir. And I obviously forgot this dir is used for the rsyslogd socket. Now I wonder if I should just stop shipping rsyslogd.conf file entirely, instead of creating the dev subdir. The prob here is that static rsyslogd.conf does not help with other postfix instances. This was the reason why creation of this subdir were moved from d/rules into configure-instance script - because this subdir is needed by every instance, not just the main one. Yet anyway, the single-instance config is the most common one. For now I'll just ship /var/spool/postfix/dev/ dir, but this is sort of a half-backed solution. Thanks, /mjt
