In that situation, it is preferable to
install manuals once, in a central location, rather than installing them for each new
machine that is later brought up. For example, the first machine??™s m4 build file might
contain this:
define(`confMANROOT??, `/usr/local/man/cat??)
Then, the m4 build files for all future machines might contain this:
define(`confNO_MAN_BUILD??)
define(`confNO_MAN_INSTALL??)
Here, the first line prevents the formatted manuals from being created. The second line
prevents the nonexistent manuals from being installed.
2.7.46 confNO_STATISTICS_INSTALL
Prevent installation of the statistics file Build macro
The sendmail statistics file is ordinarily installed automatically:
cp /dev/null statistics
install -c -o bin -g bin -m 444 statistics /etc/mail/statistics
There are legitimate reasons to suppress the installation of this statistics file. Consider a site
that has written custom software to monitor the sendmail program??™s performance. Sucha
site might wish to eliminate the sendmail statistics file because it is redundant. To prevent
installation of the statistics file, you can define this confNO_STATISTICS_INSTALL macro:
define(`confNO_STATISTICS_INSTALL??)
Withth is line in your m4 build file, the earlier install line will be eliminated during
installation.
2.7.47 confOBJADD
Extra .o files to be linked in all programs Build macro
The confOBJADD macro defines additional object files that need to be included in sendmail
and the programs associated with it (such as praliases).
Pages:
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191