Chris McDonough wrote: > The right way to do this is I think to not try to use pidproxy at > all. Instead more recent versions of Pound allow you to prevent them > from being daemonized via an option in the config file (which is the > right way to run it under supervisor): > > Daemon 0|1 > Have Pound run in the foreground (if 0) or as a daemon > (if 1). > By default Pound runs as a daemon (detaches itself from > the con- > trolling terminal and puts itself in the background). > By speci- > fying this option you can force Pound to work like a > regular > process. Useful for debugging or if you want to use > something > like daemontools. > > HTH, > > - C
Thanks Chris, this worked: [program:pound] command = /opt/intranet/parts/poundbuild/sbin/pound -p /opt/intranet/parts/poundconfig/var/pound.pid -f /opt/intranet/parts/poundconfig/etc/pound.cfg process_name = pound priority = 2 redirect_stderr = true #daemon = 0 (note: setting daemon=0 in supervisord.conf did not work, but setting it in pound.cfg did.) _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
