> 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 -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
