William A. Rowe, Jr. wrote:
At 04:47 PM 12/22/2003, Stas Bekman wrote:
I'm not sure this is a good idea to run it on the main host. If it was we
could just as well run post_config for each vhost as well.
No, you missed my earlier point. post_config is a run-once. host_init is
the run-each
No... the default server is still a server. But you make an interesting point, that
certain percolation occurs in the post config. I suppose I would want that to
happen before my handlers dealt with the per-vhost settings, and I would not
want the changes I make to that global server to
William A. Rowe, Jr. wrote:
It is almost worth a totally different hook entry point (before
post_config) such as vhost_init which *would* be called per-vhost
(starting from the main server config and working through the list.)
I have several modules with the for (s=_server; s; s = s-next)
Only question below is should this hook always run before or after the post
config hook? My gut says after post config.
At 11:19 AM 12/22/2003, Geoff wrote:
I had some spare time and thought I could help with the grunt work - my try
at a patch attached.
+for (s = server_conf; s; s =
William A. Rowe, Jr. wrote:
Only question below is should this hook always run before or after the
post config hook? My gut says after post config.
just going from what you had said earlier:
It is almost worth a totally different hook entry point (before
post_config) such as vhost_init
Geoffrey Young wrote:
William A. Rowe, Jr. wrote:
Only question below is should this hook always run before or after the
post config hook? My gut says after post config.
just going from what you had said earlier:
It is almost worth a totally different hook entry point (before
post_config)
At 04:47 PM 12/22/2003, Stas Bekman wrote:
I'm not sure this is a good idea to run it on the main host. If it was we could just
as well run post_config for each vhost as well.
No, you missed my earlier point. post_config is a run-once. host_init is the
run-each you requested.
The problem is
We have users who want to run different post_config hooks for different
vhosts. Any chance httpd-2.0 can be changed to run the open_logs/post_config
(or at least post_config) hooks for each vhost as well? Any reason for not
doing that in first place?
We have users who want to run different post_config hooks for different
vhosts. Any chance httpd-2.0 can be changed to run the open_logs/post_config
(or at least post_config) hooks for each vhost as well? Any reason for not
doing that in first place?
You can access your virtual hosts in the
Sander Temme wrote:
We have users who want to run different post_config hooks for different
vhosts. Any chance httpd-2.0 can be changed to run the open_logs/post_config
(or at least post_config) hooks for each vhost as well? Any reason for not
doing that in first place?
You can access your
At 03:36 AM 12/21/2003, Stas Bekman wrote:
We have users who want to run different post_config hooks for different vhosts. Any
chance httpd-2.0 can be changed to run the open_logs/post_config (or at least
post_config) hooks for each vhost as well? Any reason for not doing that in first
place?
11 matches
Mail list logo
