Re: help on <Directory> directive

[Brestin Sebastian <sebastianbrestin@xxxxxxxxx>]

Yes, this is the case. It is a possibility that "dir" could not exist. Also I do not have the any other access to the "server" other than read permission. So I would like to configure somehow apache to start even thought the path is unreachable.

"Dir" is actually a cache folder. But this "dir" could not exist depending on the network administration. I want apache to take advantage of that cache folder if it exists elsewhere it will serve the request from internet.

The current configuration that does not work consists in:

Alias /path /server/dir

<Directory "/server/dir">
#config
</Directory>

If I remove remove Directory directive it is works, but I need the Directory directive as well.
So any ideas?

On Tue, Apr 17, 2012 at 5:28 PM, Mark H. Wood <mwood@xxxxxxxxx> wrote:

On Tue, Apr 17, 2012 at 09:40:03AM +0300, Brestin Sebastian wrote:
> Hello,
> Why if I am using <Directory "/server/dir"> and the server is offline I get
> invalid path and apache will not start? How could I manage this?

More detail would be helpful, but it looks like you are mounting a
storage server across a network onto /server, yes?  If there is
nothing mounted at /server, what do you see?  If there is not a local
path /server/dir and the server is not mounted over /server then
"/server/dir" is indeed an invalid path.  (So far as the local
filesystem is concerned, it is the same case as if the storage *is*
mounted at /server but there is no subdirectory "dir" in the root of
that remote volume.)

If HTTPD must start even though the storage server is not mounted, you
could make an empty directory "dir" under the local "/server" and I
think that would satisfy the HTTPD configuration interpreter.

--
Mark H. Wood, Lead System Programmer   mwood@xxxxxxxxx
Asking whether markets are efficient is like asking whether people are smart.