Prev: Scalable
Next: Google generating it's own reject codes?
From: Jay G. Scott on 12 Feb 2010 15:25

Greetings,

the aliases files are limited to 1024 chars/record because of NIS.

but postfix looks like it would take hash maps instead for things
like aliases. does this work around the 1024 character limit?
i hope, i hope. the chaining biz is annoying.

j.

From: Michael Tokarev on 12 Feb 2010 15:59
Jay G. Scott wrote:
> Greetings,
>
> the aliases files are limited to 1024 chars/record because of NIS.

Which part of the postfix documentation states this?

/mjt

From: Wietse Venema on 12 Feb 2010 16:06
Jay G. Scott:
>
> Greetings,
>
> the aliases files are limited to 1024 chars/record because of NIS.
>
> but postfix looks like it would take hash maps instead for things
> like aliases. does this work around the 1024 character limit?
> i hope, i hope. the chaining biz is annoying.

hash and btree tables solve that problem.

Postfix does not enforce a length limit when it creates database
records. If the underlying database allows jumbo-sized records
then Postfix will happily store them.

The 1024-byte limit comes from Sun's ndbm implementation (*) which
was historically used to store the NIS tables. Other NIS
implementations may use different databases with different limits.

Wietse

(*) From the ndbm manpage:
The sum of the sizes of a key/content pair must not exceed
the internal block size (currently 1024 bytes). Moreover all
key/content pairs that hash together must fit on a single
block. dbm_store() will return an error in the event that a
disk block fills with inseparable data.

 | 
Pages: 1
Prev: Scalable
Next: Google generating it's own reject codes?