tration
> -Original Message-
> From: Jeff Cauhape [mailto:jpcauh...@nvdetr.org]
> Sent: Monday, May 15, 2017 16:22
> To: users@httpd.apache.org
> Subject: RE: [users@httpd] A curious thing - apachectl status in
> Apache 2.4.25
>
> EXTERNAL EMAIL
>
>
> Eric,
ape [mailto:jpcauh...@nvdetr.org]
> Sent: Monday, May 15, 2017 16:22
> To: users@httpd.apache.org
> Subject: RE: [users@httpd] A curious thing - apachectl status in Apache 2.4.25
>
> EXTERNAL EMAIL
>
>
> Eric,
>
> Yes, I went from 2.4.6 bundled with Red Hat to
re are none, it echoes "It's DEAD, Jim!". Otherwise It echoes "It's
ALIVE!!!".
That seems pretty clear.
Jeff
-Original Message-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Monday, May 15, 2017 10:24 AM
To: users@httpd.apache.org
Subject: Re: [users
On Mon, May 15, 2017 at 1:22 PM, Jeff Cauhape wrote:
> In the Apache 2.4.6 shell script apachectl, a call to “apachectl status”
>
> invokes systemctl status httpd.service. This gives you easy-to-read
>
> output regardless if the server is running or not.
Did you go from a vendor package to a sou
I recently built Apache 2.4.25 and am running it on RHEL 7.3.
I've found something that seems a step backwards from 2.4.6
and I'm hoping someone can shed some light on it.
In the Apache 2.4.6 shell script apachectl, a call to "apachectl status"
invokes systemctl status httpd.service. This gives y
