6 msgDSN relay host
1 msgRestrict sender and from to one domain on outbo...
10 msgOutbound postfix routing issue
25 msgProblem with Black List
3 msgLooking at new mail server layout

why every minute: 'reload configuration /etc/po...
\ Andy Spiegl (7 May 2008)
. \ (Wietse Venema) (7 May 2008)
. . \ Andy Spiegl (8 May 2008)
. . . \ Ralf Hildebrandt (8 May 2008)
. . . . \ Arne Hoffmann (8 May 2008)
. . . . \ Andy Spiegl (8 May 2008)
. . . . . \ Victor Duchovni (8 May 2008)
. . . . . . \ Ralf Hildebrandt (8 May 2008)
. . . . . \ Arne Hoffmann (8 May 2008)
. . . . . \ Bill Cole (8 May 2008)
. . . . . . \ Andy Spiegl (9 May 2008)
. . . . . . . \ (Wietse Venema) (9 May 2008)
. . . . . . . . \ Andy Spiegl (9 May 2008)
. . . . . . . . . \ (Wietse Venema) (9 May 2008)
. . . . . . . . . \ Bill Cole (9 May 2008)
. . . . . . . . . . \ Ralf Hildebrandt (9 May 2008)
. . . . . . . . . . . \ Ralf Hildebrandt (9 May 2008)
. . . . . . . . . . . . \ (Wietse Venema) (9 May 2008)
. . . . . . . . . . . . . \ Harald Koch (9 May 2008)
. . . . . . . . . . . . . . \ Ralf Hildebrandt (9 May 2008)
. . . . . . . . . . . . \ Bill Cole (9 May 2008)
. . . . . . . . . . . . . \ (Wietse Venema) (9 May 2008)
. . . \ (Wietse Venema) (8 May 2008)
. . . \ Tomasz Suchodolski (8 May 2008)
. . . . \ Andy Spiegl (8 May 2008)
. . . . . \ Victor Duchovni (8 May 2008)

2 msgmyhostname parameter
17 msgRBL problems with smarthost on private address ...
34 msgBackscatting filter?
3 msghow to setup postfix in 'deliver-only' mode?
7 msgSlow queue configuration
17 msgSome Windows SMTP Server have problems with STA...
5 msgFor each check_ns or each check_mx, the value i...
4 msgpostfix and spf
2 msgPassword Validation in postfix
4 msgcatching some spam with warn_if_reject and reje...
9 msgRFC: Check mail quota at a mail relay (backscat...
31 msgGPS vs GLD (greylisting)
3 msgUnmeant update from 2.2.10 to 2.5.1
27 msgmailq lockups
Subject:Re: why every minute: 'reload configuration /etc/postfix' - SOLVED
Group:Postfix-users
From:(Wietse Venema)
Date:9 May 2008


 
Bill Cole:
> At 4:30 PM +0200 5/9/08, Ralf Hildebrandt wrote:
> [...]
> >A named/BIND9 restart/stop/start did always invoke:
> >echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.named
> >and this caused postfix to be signalled by resolvconf (after all, the
> >resolv.conf changed!)
>
> This wanders back into Postfix relevance perhaps...
>
> Is there really some reason that one would want to restart/reload
> Postfix arbitrarily on all resolv.conf changes? It seems to me that
> this would be a judgment call, since so many of the things one
> *might* do to resolv.conf would not cause trouble for whatever
> persistent or semi-persistent DNS state Postfix might be retaining.

On a client box, maybe.

On a production server, definitely not.

Postfix network processes are by design short-lived so they pickup
resolv.conf and other changes on the fly. Unless the machine is
only up for a few minutes at a time, Postfix will push out the mail
eventually anyway.

> I don't oppose allowing admins to be lazy when it is feasible, but
> this strikes me as a case where sparing root from engaging in a small
> amount of thought could be somewhat expensive.

I think this is a result of peecee mentality.

Wietse


© 2004-2008 readlist.com