Suraj Kurapati <[email protected]> wrote: > Eric Wong wrote: > > [PATCH] configurator: listen :umask parameter for UNIX sockets > > Hi Eric, > > I'm using Unicorn 0.95.1 and I think that the :umask option is > behaving inversely. > > For example, if I specify :umask => 0600, the socket file ends up with > s---rwxrwx (same as chmod 0077) permissions. In contrast, if I > specify :umask => 0177, the socket file ends up with srw------- (same > as chmod 0600) permissions. > > Is umask normally specified as the inverse of a desired chmod?
Hi Suraj, that's how umask works. "man 2 umask" -- Eric Wong _______________________________________________ mongrel-unicorn mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn
