On 2022-01-21 16:09:06 -0500, Scott Kitterman wrote:
> On Friday, January 21, 2022 5:50:19 AM EST Vincent Lefevre wrote:
> > Moreover, I don't think that reloading the system is useful in
> > any case. AFAIK, the resolv.conf file is not used directly by
> > postfix itself, but by the C library,
On 2022-01-21 11:17:56 +0100, Vincent Lefevre wrote:
> On 2022-01-21 00:55:09 -0500, Scott Kitterman wrote:
> > Thanks. I've added another commit to document this in README.Debian and to
> > not enable these on install (since reloading the system does have a cost
> > and
> > this isn't
On 2022-01-21 00:55:09 -0500, Scott Kitterman wrote:
> Thanks. I've added another commit to document this in README.Debian and to
> not enable these on install (since reloading the system does have a cost and
> this isn't relevant for most systems). It will be included in the next
> upload.
On 2022-01-18 18:43:55 -0500, Scott Kitterman wrote:
> I have committed a systemd path unit based solution to git (I assume non-
> systemd users can continue to use resolvconf). I don't have a good way to
> test it, since I don't currently have an unstable system and systemd doesn't
> mix well
Package: postfix
Version: 3.6.3-4
Severity: wishlist
The postfix daemons keep a copy of /etc/resolv.conf in their chroot,
which becomes obsolete if /etc/resolv.conf changes. In bug 964762, a
suggestion was to install resolvconf, as the postfix package provides
5 matches
Mail list logo
