1 P
\bPo
\bos
\bst
\btf
\bfi
\bix
\bx a
\ban
\bnd
\bd U
\bUl
\blt
\btr
\bri
\bix
\bx
3 -------------------------------------------------------------------------------
5 P
\bPo
\bos
\bst
\btf
\bfi
\bix
\bx o
\bon
\bn U
\bUl
\blt
\btr
\bri
\bix
\bx
7 This document is probably only of historical value, because Ultrix version 4
8 dates from the early 1990s. However, as long as Wietse keeps Postfix alive for
9 SunOS 4, it is likely to run on Ultrix 4 with very little change. Feedback is
10 welcome if anyone actually still uses Postfix on any version of Ultrix.
12 The source of this document is an email message by Christian von Roques that
13 was sent on Jun 2, 1999.
15 I've upgraded the MTA of our DECstation-3100 running Ultrix4.3a to postfix-
16 19990317-pl05 and am sending you the patches I needed to get it running
21 One of the bugs of Ultrix's /bin/sh is that shell-variables set in
22 arguments of `:' expand to garbage if expanded in here-documents. Using a
23 different shell helps. I needed to replace all calls of ``sh .../makedefs''
24 by ``$(SHELL) .../makedefs'' in all the Makefile.in and am now able to use
25 ``make SHELL=/bin/sh5'' or zsh.
29 Ultrix's FD_SET_SIZE is 4096, but getdtablesize() returns 64 by default, if
30 not increased when building a new kernel. getrlimit() doesn't know
31 RLIMIT_NOFILE. This makes event_init() always log the warning: `could
32 allocate space for only 64 open files'.
34 I just reduced the threshold from 256 to 64, but this is not good. The
35 initial problem still remains: How to disable this warning on Ultrix
36 without making the source ugly?
38 To work around the first problem, all the Makefile.in files have been updated
39 to use `$(SHELL)' instead of `sh'. So you only need to supply a non-default
40 shell in order to eliminate Ultrix shell trouble.
42 To work around the latter, util/sys_defs.h was updated for Ultrix, with a
43 default FD_SETSIZE of 100. This should be sufficient for a workstation. Even in
44 1999, no-one would run a major mail hub on Ultrix 4.