I've an apache 2.2 server running Django. There exists a network drive T: which we want constant use of inside our Django application. When running Apache like a service, we can't access this drive, so far as any django code is worried the drive doesn't exist.

Basically add...

<Directory "t:/">
       Options Indexes FollowSymLinks MultiViews
       AllowOverride None
       Order allow,deny
       allow from all
</Directory>

towards the httpd.conf file the service no more runs, however i can begin apache like a console and delay pills work fine, Django will find the network drive and get up.

Why it is possible to distinction between the console and also the service? If there is a positive change? I've the service using my very own login so theoretically it will have a similar access when i do.

I am keen to help keep it running like a service as it is much less obtrusive when I am focusing on the server (unless of course there's a method to hide the console?). Any help could be most appreciated.

Advertising media are it as being something would you run it as being a nearby System account or like a User Account? It's selected within the Login tab from the "qualities" appear in the services tool in the "Administrative Tools" item within the user interface. Also, my apache does not like drive letters, you need to provide UNC's (//server/share/). I've been getting plenty of flaky network drive behavior from Apache on Home windows, too.