Precisely. With regard to PAM, I think the answer is no. Authentication/Authorization for the XMLRPC API are done using configured username/password. The risk is somewhat limited by the fact that it can use a unix domain socket so that at least exposure is limited to the machine.<br>
<br><div class="gmail_quote">On Wed, Mar 4, 2009 at 1:42 AM, Grzegorz Nosek <span dir="ltr"><<a href="mailto:grzegorz.nosek@gmail.com">grzegorz.nosek@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On śro, mar 04, 2009 at 12:55:01 -0800, mike wrote:<br>
> Why not just make a php-fpm style thing like we talked about?<br>
><br>
> Define pools of fastcgi resources, with various configuration options,<br>
> timeout thresholds, error logging/capturing perhaps, ability to run as<br>
> different uid/gid per pool, adaptive process spawning (hard limits<br>
> etc.) ...<br>
<br>
</div>[disclaimer: I haven't worked with supervisord yet, so I'm possibly<br>
wrong about its capabilities]<br>
<br>
Well, this is the foundation, which AIUI supervisord provides. However,<br>
it has no possibility to know how busy the managed processes are and<br>
when to spawn/kill (again, php-fpm has it too easy, it's not implementable<br>
this way in a generic process manager). Thus it needs some notification<br>
from Nginx when it's overloaded (and when backends are idle -- but this<br>
is a harder task).<br>
<br>
So, to recap: supervisord alone allows you to run a statically-sized<br>
pool of processes (with some nifty features like you mentioned above).<br>
<br>
If you need dynamic pool sizing, you need some external help, either from<br>
Nginx, or possibly the kernel. What we're discussing here is not an<br>
alternative to a dynamic process pool, it's one of the few sensible ways<br>
to implement it in a language-agnostic way.<br>
<br>
(BTW, I wonder whether supervisord can interface with PAM)<br>
<br>
Best regards,<br>
<font color="#888888"> Grzegorz Nosek<br>
<br>
</font></blockquote></div><br>