Milter-greylist

Hi,

The socket mode configuration(*) affects PID file mode
because milter-greylist uses umask(2) for the configuration.

(*) socket "/var/milter-greylist/milter-greylist.sock" 660

We will use the socket mode configuration to access
milter-greylist socket by other process that belongs to
group of milter-greylist process. In the case, we will use
660 for permitting group access. But it causes that PID file
also gets 660 permission. It's not expected behavior.

chmod(2) should be used instead of umask(2):
  http://www.clear-code.com/~kou/patches/milter-greylist-socket-mode.diff


Thanks,
--
kou

Kouhei Sutou <kou@...> wrote:

> chmod(2) should be used instead of umask(2):
>   http://www.clear-code.com/~kou/patches/milter-greylist-socket-mode.diff

Got it!

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...