> Date: Sat, 5 Feb 2011 19:38:42 +0100 > From: [email protected] > To: [email protected] > Subject: Re: [uWSGI] Preserve UID/GID on master process > > > > > > UID/GID should be preserved in the master process. > > For example when starting uwsgi system-wide it chdir() with UID/GID 0. > > After setuid()/setgid() to any other ID, then send a HUP it keeps the > > privileges that it has changed to. > > Which in turn may result in permission denies. > > > > So, to sum it up: > > Changin UID/GID on the master process results in unpredictable permission > > errors. > > > > > > This was already discussed, and the common sense is: it depends. > > The first idea was to add a --master-as-root option, but currently the > emperor mode is a better solution to manage multiple uid/gid/apps > > Obviously --master-as-root will be added (i still have not investigated > how complex would be implementing it, i cannot exclude that it can came up > in the stable branch soon) > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi Oh excellent, sorry I thought I had searched through the archives for it. For reference sake you could have a look at how nginx does it, their master process does always run as the UID/GID it was compiled against.
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
