#1 — iw.pound recipe does not handle all of pound's configuration options

by Carlos de la Guardia — last modified Jan 03, 2009 04:42 AM
State Confirmed
Area Functionality
Issue type Feature
Severity Medium
Submitted by Carlos de la Guardia
Submitted on Mar 26, 2008
Responsible Alter Way Solutions
Return to tracker
Sometimes, it is desirable for the recipe user to pass further options to the pound configuration, and this recipe doesn't seem to be able to do so. In my case, I wanted to set the Daemon option to 0, to be able to use the supervisor process manager with pound.
Added by Alter Way Solutions on Mar 26, 2008 09:21 AM
Issue state: unconfirmed → open
Responsible manager: (UNASSIGNED) → ingeniweb
the "pound" script is always daemonized and this recipe just creates a facility script in the buildout bin directory that looks like this:

pound_binary -f pound.cfg -p pound_pid

From there, you can control the daemon using poundctl.
Using a supervisor would just be a matter of calling the script and tracking its PID,
but in that case, you need to call the original binary directly.

Let me know if you have an issue with this

Added by (anonymous) on Mar 26, 2008 12:56 PM
The recipe creates a configuration file, pound.cfg, inside the etc directory. Pound will always start daemonized unless Daemon is set to 0 in that configuration file. What I suggested is that the recipe accepts all of pound's configuration directives so that this can be done without editing the file every time after running bin/buildout. This suggested feature would be useful for other more frequent configuration needs, like setting the timeout value or the SSL engine.
Added by (anonymous) on Mar 26, 2008 02:11 PM
Oh right, sorry I missed that option,

We'll add:

- SSLEngine
- RootJail
- LogLevel
- Alive
- LogFacility
- Daemon
- DynScale
- Client
- TimeOut
- Grace
- Control

Thanks
Added by Tarek Ziade on Jun 10, 2008 09:51 AM
fixed in 0.3.0

No responses can be added.