Hi Dave,
I had the same problem. The error is occurring because mod_actions is
not loaded in your apache configuration. Either add it to httpd.conf, or
if you're using debian, do a:
$ dpkg-reconfigure apache
and mark "mod_actions" with a [*]
Then it will work.
Comment to debian package m
Hi Dave,
I had the same problem. The error is occurring because mod_actions is
not loaded in your apache configuration. Either add it to httpd.conf, or
if you're using debian, do a:
$ dpkg-reconfigure apache
and mark "mod_actions" with a [*]
Then it will work.
Comment to debian package maint
On Mon, Jul 07, 2003 at 02:04:49PM +1000, Russell Coker wrote:
> Yes. However if Apache does the wrong thing (eg goes into an infinite loop
> in
> a library - something I've seen many times) then it may run forever if there
> is nothing to stop it. inetd will not stop it.
>
> For Apache run a
On Mon, 7 Jul 2003 10:39, Paul Bryan wrote:
> > If Apache decides not to die then most (all?) inetd programs will happily
> > allow it to do so.
[...]
> Only serving a single connection makes sense to me, as otherwise it seems
> to defeat the purpose of using inetd in the first place. In any event,
On Mon, Jul 07, 2003 at 02:04:49PM +1000, Russell Coker wrote:
> Yes. However if Apache does the wrong thing (eg goes into an infinite loop in
> a library - something I've seen many times) then it may run forever if there
> is nothing to stop it. inetd will not stop it.
>
> For Apache run as a
On Mon, 7 Jul 2003 10:39, Paul Bryan wrote:
> > If Apache decides not to die then most (all?) inetd programs will happily
> > allow it to do so.
[...]
> Only serving a single connection makes sense to me, as otherwise it seems
> to defeat the purpose of using inetd in the first place. In any event,
On Mon, Jul 07, 2003 at 01:17:25AM +1000, Russell Coker wrote:
> inetd does not kill the Apache process,
True, my bad...
> If Apache decides not to die then most (all?) inetd programs will happily
> allow it to do so.
>From the apache site:
For each http connection received, a new cop
On Mon, Jul 07, 2003 at 01:17:25AM +1000, Russell Coker wrote:
> inetd does not kill the Apache process,
True, my bad...
> If Apache decides not to die then most (all?) inetd programs will happily
> allow it to do so.
>From the apache site:
For each http connection received, a new cop
On Sun, 6 Jul 2003 23:35, Paul Bryan wrote:
> That's exactly right. Whenever a request comes in on port 80, inetd starts
> up an apache process to handle it. Once the request is completed, inetd
> kills the apache process.
inetd does not kill the Apache process, it reaps (via wait()) the Apache
p
On Sun, Jul 06, 2003 at 02:05:23PM +0200, mi wrote:
> It seems any server process is terminated immediateley after every single
> request from a broser. In other words, a 'ps aux' doesn't show any apache
> process when my browser opens localhost:80; only a 'top' does for short.
> Every single pa
On Sun, 6 Jul 2003 23:35, Paul Bryan wrote:
> That's exactly right. Whenever a request comes in on port 80, inetd starts
> up an apache process to handle it. Once the request is completed, inetd
> kills the apache process.
inetd does not kill the Apache process, it reaps (via wait()) the Apache
p
On Sun, Jul 06, 2003 at 02:05:23PM +0200, mi wrote:
> It seems any server process is terminated immediateley after every single
> request from a broser. In other words, a 'ps aux' doesn't show any apache
> process when my browser opens localhost:80; only a 'top' does for short.
> Every single pa
12 matches
Mail list logo
