Re: [Apachetoolbox-devel] Re: mod_watch in .58: improved (bin attached)

[Toni M. <su...@oe...>]

Hi Kevin,

On Fri, Jul 12, 2002 at 11:14:17AM -0700, Kevin J. Menard, Jr. wrote:
> Ok, I got mod_watch all working now.  It looks for apxs in a bunch of 
> different spots (mine is always in /usr/local/apache/bin, but I don't 
> know if someone might put it in /usr/bin or something).

well, after feeling the need for different Apache versions I started
out with something like /usr/local/stow/apache-1.3.26 as the root of
the tree, but quickly found that I'd rather have made this
/usr/local/stow/apache-1.3.26.<n> with n = 1, 2, 3, ... or something
else explaining the difference (ie, module&option selections).

> Mine worked fine without the ranlib thing.  So, in the beta I plan on 

Which platform?

> throwing up some time this weekend, I'll leave it commented out so I can 
> see what other people are experiencing.  If it's a problem, just remove 

Ok.

> never even notice this mod, and now that I see it, it looks pretty cool. 
>   I was looking for per virt host mrtg output :)

AFAIR this module still has a severe problem (imho) which is that it
needs to place the collected statistics in a file or directory (don't
remember which) that is determined at compile time instead of having
run time configuration directives. Unfortunately this precludes running
several instances of Apache which use this module on the same machine
(bummer #1). Problem #2 is that the locations in question tend to be
writable only by root. I'd very much prefer to have full configurability
on all modules so as to be able to have self-contained trees which
might eg. contain one Apache instance each, and without the need to
reconfigure and recompile the whole thing for each instance. Just
in case the module's author rejected the idea of spiffing up his
module since he said it had cost him too much time already, and does
what he needs as-is.


When I started to tinker with the Apachetoolbox, I just explored the
forest of modules out there, most of which are unknown to me. There
are still modules who have slightly different names, but very similar
descriptions, and there is no hint on when to use which, or what
would happen should one include two of them. :)   At least, the
"help" file (which thankfully can be read w/o having the script
open) contains some nice information. Btw, reading it with "99"
never made sense to me - it just scrolls through despite having set
PAGER.


Best,
--Toni++