Now we will create a file called
, which, when later processed, will create
-style configuration file. The
fill will be very
small, containing only these three lines:
These three lines do everything that the preceding
11 chapters did and more. We discuss them individually, then
show how to process the file.
Naturally, a configuration is not simply plucked from thin air. Instead
the master prototype configuration needs to be
read and processed with the following command:
Note that the expression inside the parentheses begins with a reverse apostrophe
and ends with a forward one. These opposing half quotes are used by
(1) to prevent a test from being interpreted as a macro.
is taken to be the pathname of a file.
That file is read at this point as though it were actually typed in
A number of values in the configuration file will differ from operating system
to operating system. The location of the queue directory, for example,
for IRIX 5.x
BSD 4.3 Unix. To declare the proper value for your operating system, look in the
aix3.m4 bsdi1.0.m4 hpux10.m4 linux.m4 sco3.2.m4 ultrix4.m4
amdahl-uts.m4 bsdi2.0.m4 hpux9.m4 nextstep.m4 solaris2.m4 unknown.m4
aux.m4 dgux.m4 irix4.m4 osf1.m4 sunos3.5.m4
bsd4.3.m4 domainos.m4 irix5.m4 ptx2.m4 sunos4.1.m4
bsd4.4.m4 dynix3.2.m4 isc4.1.m4 riscos4.5.m4 svr4.m4
Pick the operating system closest to yours. For
SunOS 4.1.4 systems, for example, choose
Whichever you choose, include support for it by stripping the
suffix and including the resulting name in an
Remember to surround the result in a reverse and forward apostrophe pair.
The last line in our
the magic incantation of a
Two arguments inside the parentheses, separated by a comma, are
required. The first argument,
to create a null (do-nothing) client (.cf) file. The second argument
is the canonical name of the mail hub. Just as we did for the
file, we use the hostname
should, of course, use the canonical name of your own mail hub.