On 1/18/12 12:28 PM, David F. Skoll wrote: > * MIMEDefang 2.73-BETA-2 > > * Make the -G option cause files created by mimedefang to > be group-readable.
Very odd. By the time I hit mimedefang.pl:4762 the umask has been reset to 077, even with the -G flag. I put syslog()'s in mimedefang.c wherever umask was being called, and it was definitely being hit. Jan 19 14:32:28 glue01 mimedefang-multiplexor[16737]: Starting slave 0 (pid 16739) (1 running): Bringing slaves up to minSlaves (2) Jan 19 14:32:28 glue01 mimedefang[16754]: socket mask 0007 Jan 19 14:32:28 glue01 mimedefang[16754]: file mask 0027 Jan 19 14:32:28 glue01 mimedefang[16754]: IP validation header is X-MIMEDefang-Relay-22f3569ea82cd4127fda71fb6bdc49e312e7040e Jan 19 14:32:28 glue01 mimedefang[16754]: MIMEDefang alive. slavesReservedForLoopback=-1 AllowNewConnectionsToQueue=1 doRelayCheck=1 doHeloCheck=1 doSenderCheck=0 doRecipientCheck=1 Jan 19 14:32:28 glue01 mimedefang[16754]: Multiplexor alive - entering main loop Jan 19 14:32:31 glue01 mimedefang-multiplexor[16737]: Starting slave 1 (pid 16760) (2 running): Bringing slaves up to minSlaves (2) ... message arrives here ... Jan 19 14:33:08 glue01 mimedefang.pl[16739]: E40A8221496: umask: 0077 So I see one mimedefang instance (pid 16754) setting his umask... but not the other instance (16739). -Philip _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
