On чет, 30 јан 2014 08:51:41 CET, Roberto De Ioris wrote:
This is my (part of) the vassal config I use.
master-as-root = true
uid = www-data
chdir = %(site-root)
unshare = fs
hook-post-jail = mount:none none / recursive,private
hook-post-jail = mount:none %(app-root) %(site-root)/app bind,ro
If I have master-as-root set, on the first run the workers will have the
bind mounts (and the master doesn't have it).
The problems is when I touch the config file, and the emperor reloads
the vassal (the master is not killed), the hooks do not run in the workers
Is that the intended behaviour? Do I need to use another hook?
If I have master-as-root unset, the master runs the hook, and all
workers inherit that. Even after a reload. But I had to use
master-as-root because of stupid unix socket perms.
--master-as-root is generally a bad idea.
Can you describe the unix socket problem ? maybe we can find a better
workaround
different permission problems. I'll try to fix them then.
I tend to put sockets in /run/uwsgi/ which is created by the emperor
with
exec-as-root = install -d /run/uwsgi -g www-data -m770
will this snippet work in the vassal always?
socket = /run/uwsgi/%n.sock
chmod-socket = 666
chown-socket = www-data:www-data
uid = www-data
--
дамјан
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
