OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Postfix Archives: Re: a postfix programmers manual?

Re: a postfix programmers manual?

Subject: Re: a postfix programmers manual?
From: Wietse Venema (wietseporcupine.org)
Date: Fri Dec 17 1999 - 08:48:05 CST

Frank Dziuba:
> Hello,
>
> Since many of us make mods to postfix for various reasons I'm wondering if
> anyone has started to put together a 'programming manual' of sorts? (Weitse?)
>
> For example, it took us some time to decipher how Postfix opens file (what
> modules are invoked in which order and what their purposes are).

The built-in documentation will have to suffice. It makes up 40%
of the source code line count. Writing more docs means less time
to improve Postfix.

The other reason that postfix is 60% code/40% docs is that the
Postfix internals still need to be revised. That not only applies
to the protocols spoken between Postfix daemons, it probably also
applies to queue file formats and perhaps even to the break-down
of tasks across programs (for example, trivial-rewrite should do
canonical/virtual mappings).

> It would sure be great to have some sort of document started so weeding through
> the sometimes tricky code to find out where something happens wouldn't be so
> hard. It would also make it easier for others to 'conform' to the postfix
> 'coding standards'.
>
> Along that line, what the heck function could I call to just write a message
> to syslog?

All logging is done with the msg(3) interface. Its man page explains
how to have the output sent to syslogd and/or stderr.

        Wietse

This archive was generated by hypermail 2b27 : Fri Dec 17 1999 - 08:53:25 CST