OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Wietse Venema (wietse_at_porcupine.org)
Date: Mon Sep 02 2002 - 11:02:07 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    All Postfix daemons commit suicide, except for the master and the
    queue manager. With everything in Postfix, this may change when
    other long-lived processes are added.

            Wietse

    Clifton Royston:
    > On Thu, Aug 29, 2002 at 11:33:05AM -0300, Leonardo Rodrigues ( listas ) wrote:
    > >
    > > I noticed one interesting thing and I'd like to share with you, as we're
    > > talking of 'postfix reload' ....
    > >
    > > postconf seems to show new values right after editing main.cf even when
    > > 'postfix reload' or 'postfix stop; postfix start' was not issued.
    > >
    > > Question is: should postconf shows 'actual parameters' of running
    > > postfix version or should it show 'main.cf' values ???
    >
    > This is fairly closely related to the modular philosophy of postfix.
    >
    > postconf shows the picture of how the postfix system (or any piece of
    > it) would be configured *if* started now. Because postfix is not
    > monolithic, postconf can't query some one program and take its running
    > state as exemplary of the whole system.
    >
    > In particular, if the main.cf has just been updated, and postfix
    > reload was not done, different daemons may have different images of the
    > configuration, some before the change and some after the change,
    > depending on when they were started.
    >
    > As daemons deliberately suicide and are restarted over time,
    > eventually all of them should again have the same image of the
    > configuration, except in the case of changes that affect the state of
    > the master daemon (e.g. the default process limit.) Because the master
    > daemon is long-lived, changes affecting it will not automatically be
    > picked up unless a postfix reload is done.
    >
    > Gurus: do I have this right now?
    >
    > This can be expressed in a Makefile thus:
    >
    > # GNU makefile (gmake) for postfix distribution destination servers
    >
    > BIN_DIR=/usr/local/sbin
    >
    > # Locally dependent list of db files.
    > DB_MAPS=valid-users.db
    >
    > # pattern rule for generating a .db map file from its text source file
    > #
    > %.db: %
    > ${BIN_DIR}/postmap hash:$<
    >
    > db_maps: ${DB_MAPS}
    >
    > .reload: main.cf master.cf
    > touch .reload
    > ${BIN_DIR}/postfix reload
    >
    > all: ${DB_MAPS} reload
    >
    > -- Clifton
    >
    > --
    > Clifton Royston -- LavaNet Systems Architect -- cliftonrlava.net
    > "What do we need to make our world come alive?
    > What does it take to make us sing?
    > While we're waiting for the next one to arrive..." - Sisters of Mercy
    > -
    > To unsubscribe, send mail to majordomopostfix.org with content
    > (not subject): unsubscribe postfix-users
    >
    >

    -
    To unsubscribe, send mail to majordomopostfix.org with content
    (not subject): unsubscribe postfix-users