[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
Synopsis: The apache cannot reread the new added vhost(name based) ONLY. State-Changed-From-To: open-feedback State-Changed-By: marc State-Changed-When: Sat Oct 31 23:19:40 PST 1998 State-Changed-Why: First, are you sure you really need that many vhosts? If you don't have extensive configuration required for each one that is different, then you may be able to just use mod_rewrite without any virtualhosts to rewrite requests based on the Host: header. I can't duplicate your problem of using that much memory. Do you perhaps have a large number of added directives (eg. aliases) in the main server config? Those will all be inherited by each vhost. If you do, then make the main server into a vhost and move them all into that so they aren't inherited by each vhost. If that doesn't help, then please send any added config directives plus an example vhost section. The reason why it takes more memory to shutdown or restart is because the Apache process you start to do -k shutdown/restart has to read the config files to find the PID file. If you point the restart/shutdown process at a config file with only the ServerRoot and PidFile directives in (using the -d or -f command line options), then it should be faster. It is unlikely that we will ever provide any incremental adding of vhosts due to the complexity. It is not appropriate, however, for it to take the times you are reporting to start.
