13 and above).
-e ?§10.5.1.5 on page 373 Allow empty data for keys.
-f ?§10.5.1.6 on page 374 Don??™t fold uppercase to lowercase.
-l ?§10.5.1.7 on page 374 List database types supported.
-N ?§10.5.1.8 on page 374 Append a null byte to all keys.
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
372 | Chapter 10: Build and Use Companion Programs
In the following sections, we describe each switch in detail.
10.5.1.1 -c
Set the cache size for hash and btree makemap command-line switch
The -c switchinstructs makemap to set the cache size for hash or btree databases to the
number of bytes indicated:
% makemap -c 524288 hash outfile
The default cache size, if this switch is not specified, is 1,048,576 bytes (1k squared). Note
that setting the cache size is an art, and that the larger the cache, the better. The minimum
cache size is recommended to be no less than 10 pages, or about 40,960 bytes.
10.5.1.2 -C
Use an alternative sendmail configuration file makemap command-line switch
Ordinarily, makemap will leave the ownership of the created file unchanged. That is, it will
behave the same as any nonprivileged Unix program that creates files.
If the TrustedUser option (?§24.9.122 on page 1112) is set in the sendmail configuration file,
and if makemap was compiled withHASFCHOWN defined as 1, and if makemap is run by
root, the output file will become owned by the TrustedUser option??™s user.
Pages:
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672