Mercurial > masqmail
annotate docs/INSTALL.linux @ 72:ad034b57f3b2
fixed Debian bug 536060 (log files are closed after SIGHUP receival)
Explanation:
When run in daemon mode, first the log files are opened. They get
assigned to the file descriptors 3 and 4 usually. Then std{in,out,err}
are closed. When SIGHUP comes in, all open files are closes and
masqmail reexecutes itself. The new masqmail instance opens the log
files at fd 0 and 1 now, but std{in,out,err} are closed afterwards,
thus the log files are closed.
The fix is to close the log files before std{in,out,err} are closed,
in case the log files have higher fds. After std{in,out,err} were
closed, the log files get opened again, now.
See also: http://bugs.debian.org/536060
author | meillo@marmaro.de |
---|---|
date | Wed, 16 Jun 2010 10:32:20 +0200 |
parents | 4762e0d26d8e |
children | 92340177150d |
rev | line source |
---|---|
59 | 1 Distribution specific stuff |
2 =========================== | |
3 | |
4 Debian | |
5 ------ | |
6 | |
7 If you compile for Debian, do the configure with at least these options: | |
8 | |
9 ./configure --with-liblockfile --with-group=mail | |
10 | |
11 Use the group `mail' instead of the group `trusted'. | |
12 | |
13 You can also build your own Debian package with | |
14 | |
15 dpkg-buildpackage -rfakeroot | |
16 | |
17 You need to have fakeroot installed to do this. Or, as root, do: | |
18 | |
19 dpkg-buildpackage | |
20 | |
21 However, you better have a look at the official masqmail package in | |
22 Debian. | |
23 | |
24 apt-get source masqmail | |
25 | |
26 is your friend. | |
27 | |
28 | |
29 | |
30 SuSE/Redhat | |
31 ----------- | |
32 | |
33 There are spec files for rpm creation on the website. You may have to | |
34 adjust these files. |