Welcome to WebmasterWorld Guest from 184.108.40.206
For example, say my mapped network drive is Z:, I'm using:
When I put that in, apache won't start. Now here's the weird part: if I use the full UNC path (say //remote-server/shared/home/htdocs), then apache starts just fine. The problem is, the way most of the site is configured, it is looking for that /home/htdocs directory to be the site root, not that full UNC path, so everything gets messed up. And since the files get copied directly from there to the production site, I can't really be switching code back and forth. Even more strange is a co-worker's computer is the same OS and apache version as mine and his works just fine.
And just to be clear, I can connect in Windows just fine to the network drive. I've also tried running the apache service as the user I log in with instead of Local System, and that didn't work either. Any thoughts are greatly appreciated, thanks!
It is set there. We get a general error saying that Apache can't start - and it dies.
Just a question, you're BOTH using a name based configuration correct? It's been a while but I fixed something similar by specifying a different IP address for each virtual host, which is something you don't need to do with name based setups.
I will check (mattdw not around today). On mine - i use hard coded IP's.
CustomLog logs/access.log combined
CustomLog logs/taccess.log common
CustomLog logs/agent.log agent
ScriptAlias /cgi-bin /home/billthecat/webmasterworld.com/htdocs/cgi-bin
and then we just flip in/out our hosts file. snippet:
I think matt is using some wildcards for some vhosts.
I am sure we tried it both ways.
@youfoundjake - I Don't think we have trid that.
> Have you tried FileMon from Sysinternals.
> To see what files Apache is reading, or trying to read locally.
I know FileMon well. What would we be looking for there?
>Did you try to run apache via console and not via the service control manager?
ya, either way - no difference.
Just tested; running from the console, i.e., not to start the service from console via
net start ...
(running apache from console) worked for me. The problem seems to be that the scm, even if the service is set to a user account, does not repeat the network drive mapping when starting the service under user x. But that's a problem of M$ and not Apache.