On Fri, Mar 12, 2010 at 8:46 AM, Stuart Henderson wrote:
> I don't think there's much point in having apachectl parse enough
> to work this out, but maybe it's worth checking if httpd is still running
> after the HUP and printing a simple warning if not..
I agree with this
-dav
On 2010-03-12, David Coppa wrote:
> On Thu, Mar 11, 2010 at 10:39 PM, Denis Doroshenko
> wrote:
>
>> it may fail in case one uses -d and/or -f flags to the httpd (e.g.
>> sets them in /etc/rc.conf or /etc/rc.conf.local)
>
> This doesn't obey to -d too:
>
> # the path to your PID file
> PIDFILE=/va
On Thu, Mar 11, 2010 at 10:39 PM, Denis Doroshenko
wrote:
> it may fail in case one uses -d and/or -f flags to the httpd (e.g.
> sets them in /etc/rc.conf or /etc/rc.conf.local)
This doesn't obey to -d too:
# the path to your PID file
PIDFILE=/var/www/logs/httpd.pid
the problem is apachectl be
On 3/11/10, David Coppa wrote:
> Is this something utterly stupid?
>
> just wasting some time...
> david
>
> --- apachectl.orig Wed Mar 3 23:20:53 2010
> +++ apachectl Thu Mar 11 20:11:31 2010
> @@ -27,6 +27,9 @@
> # the path to your httpd binary, including options if neces
On Thu, 11 Mar 2010, Gilles Chehade wrote:
> On Thu, Mar 11, 2010 at 03:20:33PM +0100, Antoine Jacoutot wrote:
> > On Thu, 11 Mar 2010, Ozgur Kazancci wrote:
> >
> > > When apachectl issuing a restart, it sends a SIGHUP signal to httpd,
> > > and when httpd receives this signal, it doesn't exit f
On Thu, Mar 11, 2010 at 03:20:33PM +0100, Antoine Jacoutot wrote:
> On Thu, 11 Mar 2010, Ozgur Kazancci wrote:
>
> > When apachectl issuing a restart, it sends a SIGHUP signal to httpd,
> > and when httpd receives this signal, it doesn't exit from its chroot.
> > So, "apachectl restart" becomes un
On Thu, Mar 11, 2010 at 04:08:10PM +0200, Ozgur Kazancci wrote:
>When apachectl issuing a restart, it sends a SIGHUP signal to httpd,
>and when httpd receives this signal, it doesn't exit from its chroot.
>So, "apachectl restart" becomes unfunctional when you have external
>modules via LoadModule i
On Thu, 11 Mar 2010, Ozgur Kazancci wrote:
> When apachectl issuing a restart, it sends a SIGHUP signal to httpd,
> and when httpd receives this signal, it doesn't exit from its chroot.
> So, "apachectl restart" becomes unfunctional when you have external
> modules via LoadModule in your httpd.con
When apachectl issuing a restart, it sends a SIGHUP signal to httpd,
and when httpd receives this signal, it doesn't exit from its chroot.
So, "apachectl restart" becomes unfunctional when you have external
modules via LoadModule in your httpd.conf.
I have the following line in my httpd.conf:
Loa
9 matches
Mail list logo
