SMM:08-92
Sendmail Installation and Operation Guide
HASUNAME
Set this if you have the uname(2) system call (or corresponding library rou-
tine). Set by default if SYSTEM5 is set.
HASGETDTABLESIZE
Set this if you have the getdtablesize(2) system call.
HASWAITPID
Set this if you have the haswaitpid(2) system call.
FAST_PID_RECYCLE
Set this if your system can possibly reuse the same pid in the same second of
time.
SFS_TYPE
The mechanism that can be used to get file system capacity information. The
values can be one of SFS_USTAT (use the ustat(2) syscall), SFS_4ARGS (use
the four argument statfs(2) syscall), SFS_VFS (use the two argument statfs(2)
syscall including <sys/vfs.h>), SFS_MOUNT (use the two argument statfs(2)
syscall including <sys/mount.h>), SFS_STATFS (use the two argument
statfs(2) syscall including <sys/statfs.h>), SFS_STATVFS (use the two argu-
ment statfs(2) syscall including <sys/statvfs.h>), or SFS_NONE (no way to
get this information).
LA_TYPE
The load average type. Details are described below.
The are several built-in ways of computing the load average. Sendmail tries to auto-configure them
based on imperfect guesses; you can select one using the cc option -DLA_TYPE=type, where type
is:
LA_INT
The kernel stores the load average in the kernel as an array of long integers.
The actual values are scaled by a factor FSCALE (default 256).
LA_SHORT
The kernel stores the load average in the kernel as an array of short integers.
The actual values are scaled by a factor FSCALE (default 256).
LA_FLOAT
The kernel stores the load average in the kernel as an array of double precision
floats.
LA_MACH
Use MACH-style load averages.
LA_SUBR Call the getloadavg routine to get the load average as an array of doubles.
LA_ZERO
Always return zero as the load average. This is the fallback case.
If type
LA_INT
,
LA_SHORT
, or
LA_FLOAT
is specified, you may also need to specify
_PATH_UNIX
(the path to your system binary) and
LA_AVENRUN
(the name of the variable containing the load
av erage in the kernel; usually "_avenrun" or "avenrun").
6.3. Configuration in sendmail/conf.c
The following changes can be made in conf.c.
6.3.1. Built-in Header Semantics
Not all header semantics are defined in the configuration file. Header lines that should
only be included by certain mailers (as well as other more obscure semantics) must be specified
in the HdrInfo table in conf.c. This table contains the header name (which should be in all lower
case) and a set of header control flags (described below), The flags are:
H_ACHECK
Normally when the check is made to see if a header line is compatible with
a mailer, sendmail will not delete an existing line. If this flag is set, send-
mail will delete even existing header lines. That is, if this bit is set and the
mailer does not have flag bits set that intersect with the required mailer
flags in the header definition in sendmail.cf, the header line is always
deleted.