> Am 31.03.2023 um 02:48 schrieb Jan Ehrhardt :
>
> Stefan Eissing via dev in gmane.comp.apache.devel (Tue, 28 Mar 2023
> 10:16:34 +0200):
>> Am 28.03.2023 um 01:21 schrieb Robert L Mathews :
>>> On 3/16/23 5:38 AM, Stefan Eissing via dev wrote:
>>>
I am not familiar enough with
Stefan Eissing via dev in gmane.comp.apache.devel (Tue, 28 Mar 2023
10:16:34 +0200):
> Am 28.03.2023 um 01:21 schrieb Robert L Mathews :
>> On 3/16/23 5:38 AM, Stefan Eissing via dev wrote:
>>
>>> I am not familiar enough with mod_fcgi's operation to make a judgement on
>>> that.
>>
>> As a
> Am 28.03.2023 um 01:21 schrieb Robert L Mathews :
>
> On 3/16/23 5:38 AM, Stefan Eissing via dev wrote:
>
>> I am not familiar enough with mod_fcgi's operation to make a judgement on
>> that.
>
> As a followup to this, it turned out it was caused by the problem fixed here:
>
>
On 3/16/23 5:38 AM, Stefan Eissing via dev wrote:
I am not familiar enough with mod_fcgi's operation to make a judgement on that.
As a followup to this, it turned out it was caused by the problem fixed
here:
https://github.com/apache/httpd/commit/d6a9e4
When the httpd parent process
> Am 15.03.2023 um 17:27 schrieb Robert L Mathews :
>
> [I sent this message to the users list but there were no replies; trying here
> instead.]
>
> After upgrading from httpd 2.4.54 to 2.4.55, I noticed that mod_fcgid scripts
> would sometimes get "stuck" in the "working" state, rather
[I sent this message to the users list but there were no replies; trying
here instead.]
After upgrading from httpd 2.4.54 to 2.4.55, I noticed that mod_fcgid
scripts would sometimes get "stuck" in the "working" state, rather than
the "ready" state, even though the script associated with the
