On Tue, Jul 16, 2002 at 08:30:41AM -, [EMAIL PROTECTED] wrote:
> martin 2002/07/16 01:30:41
>
> Modified:support apachectl.in
> Log:
> If "@APACHECTL_ULIMIT@" is used in apachectl.in, then something must
> replace it by a sensible (platform dependent?) value upon "make insta
Cliff Woolley <[EMAIL PROTECTED]> writes:
> On Tue, 28 May 2002, Justin Erenkrantz wrote:
>
> > FWIW, I think this simplification should be in .37. But, that's
> > Cliff's call.
>
> I agree, it will.
It would be nice to have some agreement on what the big picture is
by the time 2.0.37 is rele
On Tue, 28 May 2002, Justin Erenkrantz wrote:
> FWIW, I think this simplification should be in .37. But, that's
> Cliff's call.
I agree, it will. I haven't changed any tags so far; I'm waiting for a
bit bigger batch, and then I'll tag with JCW_PRE2_2037, then
JCW_PRE3_2037, and so on. Once we
On Mon, May 27, 2002 at 11:46:01AM -, [EMAIL PROTECTED] wrote:
> trawick 02/05/27 04:46:01
>
> Modified:.CHANGES
>support apachectl.in
> Log:
> simplified apachectl...
>
> . it now uses "httpd -k verb" support for start/restart/etc.
> . it now can
On Mon, 27 May 2002, Marc Slemko wrote:
> It seems that the thing named "apachectl" has become something very
> very different from what it was created to be. The need to set certain
> environment variables before running httpd, and the need for a
> wrapper script that provides standard command
On Mon, 27 May 2002, Joshua Slive wrote:
>
> On Mon, 27 May 2002, Sascha Schumann wrote:
>
> > > -0.9. Whoever said we were deprecating them? I thought the plan was that
> > > apachectl would continue to accept 'start|stop|restart' and would pass
> > > them as 'httpd -k $ARGV' to Apache. Tha
On Mon, 27 May 2002, Sascha Schumann wrote:
> > -0.9. Whoever said we were deprecating them? I thought the plan was that
> > apachectl would continue to accept 'start|stop|restart' and would pass
> > them as 'httpd -k $ARGV' to Apache. That is what apachectl does
> > currently. Yes, you *cou
> -0.9. Whoever said we were deprecating them? I thought the plan was that
> apachectl would continue to accept 'start|stop|restart' and would pass
> them as 'httpd -k $ARGV' to Apache. That is what apachectl does
> currently. Yes, you *could* say apachectl -k start with the new code and
> it
On 27 May 2002, Jeff Trawick wrote:
> > Looks good. If we are officially deprecating the non -k options, do
> > we want to warn the user? ie.
> > echo "Option 'start' is deprecated, use 'apachectl -k start'"
>
> +1 from me
-0.9. Whoever said we were deprecating them? I thought the plan was t
Joshua Slive <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
> > trawick 02/05/27 04:46:01
> > Modified:.CHANGES
> >support apachectl.in
> > Log:
> > simplified apachectl...
> > . it now uses "httpd -k verb" support for start/restart/etc.
> > .
[EMAIL PROTECTED] wrote:
> trawick 02/05/27 04:46:01
>
> Modified:.CHANGES
>support apachectl.in
> Log:
> simplified apachectl...
>
> . it now uses "httpd -k verb" support for start/restart/etc.
> . it now can pass through any httpd option, so apachec
> [EMAIL PROTECTED] wrote:
> >
> > Switch back to SIGUSR1 for graceful restarts on all platforms that
> > support it. This defines a symbol called AP_SIG_GRACEFUL in
> > ap_config_auto.h which will have the appropriate signal value. All
> > direct references to SIGWINCH have been replaced with
[EMAIL PROTECTED] wrote:
>
> Switch back to SIGUSR1 for graceful restarts on all platforms that
> support it. This defines a symbol called AP_SIG_GRACEFUL in
> ap_config_auto.h which will have the appropriate signal value. All
> direct references to SIGWINCH have been replaced with AP_SIG_GRACE
13 matches
Mail list logo
