Hi guys:
Wow... what a long thread...
IMHO, the best solution here is to look at apache's main loop
implementation and adapt our code. This way, (hopefully) we will get
what we want (late initialization) without modifying any apr code.
Carlo, since you seem to be on a roll here, could you pleas
On Fri, Dec 11, 2009 at 08:59:56AM -0700, Brad Nicholes wrote:
>
> APR is designed to solve these problems in a cross platform way and we
> are proposing that we abandon the cross platform solution in favor of a
> platform specific solution.
Just want to clarify here that it is not a "platform sp
Brad Nicholes wrote:
On 12/11/2009 at 6:21 AM, in message <4b224750.2090...@pocock.com.au>,
Daniel
> Pocock wrote:
>
>
>>> it replaces apr_proc_detach with an inline implementation of it on plain
>>> POSIX and that should be most likely as portable (at least for the pla
>>> On 12/11/2009 at 6:21 AM, in message <4b224750.2090...@pocock.com.au>,
>>> Daniel
Pocock wrote:
>> it replaces apr_proc_detach with an inline implementation of it on plain
>> POSIX and that should be most likely as portable (at least for the platforms
>> we care of) and doesn't intentionally
Spike Spiegel wrote:
> On Wed, Nov 25, 2009 at 4:20 PM, Daniel Pocock wrote:
>
>> One problem I've been wondering about recently is the scalability of
>> gmetad/rrdtool.
>>
>
> [cut]
>
>
>> In a particularly large organisation, moving around the RRD files as
>> clusters grow could becom
> it replaces apr_proc_detach with an inline implementation of it on plain
> POSIX and that should be most likely as portable (at least for the platforms
> we care of) and doesn't intentionally include any error checking to make it
>
How about Cygwin and mingw? I'm not sure if the use of pipe(
