If I set the vars in my ~/.bashrc and start Supervisor from the command line, that does work. In fact, because I had the vars set there in addition to in supervisord.conf, the problem was hidden. Everything worked as expected from the command line but not when the server was rebooted, because I start supervisor with a cron @reboot line, and ~/.bashrc isn't sourced.
I already checked out the Supervisor source and poked around some. Tomorrow I'll see if I can dig into this a bit more and figure out what's really happening. On Thu, Sep 16, 2010 at 6:39 PM, Chris McDonough <[email protected]> wrote: > It should work that way, yes. Does it work to set the envvars in the > terminal process used to start up supverisord for you? > > On Thu, 2010-09-16 at 16:28 -0700, Wyatt Baldwin wrote: > > I'm running Supervisor 3.0a9 and trying to set some global environment > > variables in the supervisord section of my supervisord.conf. > > > > The way I read the docs, the `environment` setting in the supervisord > > section should be passed down to the various program sections and from > > there to the commands being run, but this isn't happening. When I copy > > the `environment` setting to the program sections, everything works as > > expected. > > > > So, am I misunderstanding the docs? Is this a known issue? > > _______________________________________________ > > Supervisor-users mailing list > > [email protected] > > http://lists.supervisord.org/mailman/listinfo/supervisor-users > > >
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
