Nerijus Baliunas <nerijus@...> wrote: > And I'm getting this message in the logs: milter-greylist: Error defining > access to /var/milter-greylist/milter-greylist.sock: No such file or > directory Yes, it seems to be created from smfi_main() > It seems socket is not created in smfi_setconn()? I tried to move chmod() > after "exitval = smfi_main()" line, but it didn't work neither. Sure: this is never reached in normal condition. > It seems the best > option would be to use umask(), but then it's impossible to use syntax like > socket "/foo/bar/sock" 660, isn't it? I have two concerns: - can we screw things in smfi_main() by tempering with umask()? - doesn't smfi_main() set umask() to avoid such problems? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@...
Message
Re: [milter-greylist] group permissions for socket
2007-02-04 by manu@netbsd.org
Attachments
- No local attachments were found for this message.