Dear reader,
The explanation for changing a directory is the following:
ZM_DIR_EVENTS
This is the path to the events directory where all the event images and other miscellaneous files are stored. It is normally given as a subdirectory of the web directory you have specified earlier however if disk space is tight it can reside on another partition in which case you should create a link from that area to the path you give here.
However whatever I try I am not able to have the images stored elsewhere. I tried several things:
1) To have the directory under "/home/paul/events/"
This did not work out.
2) I left the specified directory as "events" and I removed: under /var/www/html/events/ the "1" subdirectory.
There I made:
ln -s /home/paul/events/1 1
and I created under /home/paul/events/ a "1" directory.
However all in vain.
Cheers,
Paul
Problems with specifying another directory.
-
- Posts: 22
- Joined: Wed Dec 06, 2006 10:30 pm
- Location: The Netherlands
-
- Posts: 247
- Joined: Sun Jan 16, 2005 11:26 am
-
- Posts: 22
- Joined: Wed Dec 06, 2006 10:30 pm
- Location: The Netherlands
Doesn't anybody know?
Hi out there,
I tried out a lot of things but none seem to get it running.
I have now put it at:
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/var/www/html">
Options FollowSymLinks
AllowOverride All
</Directory>
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
# Options Indexes FollowSymLinks
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
But nothing changes.
Thanks,
Paul
I tried out a lot of things but none seem to get it running.
I have now put it at:
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/var/www/html">
Options FollowSymLinks
AllowOverride All
</Directory>
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
# Options Indexes FollowSymLinks
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
But nothing changes.
Thanks,
Paul
What, exactly, is the error message or symptom you see what you change it?
Possibilities (if you aren't seeing images but they ARE being created)
Apache doesn't have adequate permissions. Chown the directories to apache's process name, or "chmod -R 777 /new/path" for an insecure quick fix. (Not advised unless you have no other users on your box)
Also, when I check mine (I use a different drive for events), I don't have a trailing slash after the path. Eg
cameras/events
(Which is linked symbolically to a different drive - also works if I specify it directly).
This may be a red herring and ZA is smart enough to strip trailing slashes if not required.
Oh, and when you change Apache's config you need to restart it - in case you didn't. apachectl restart
Possibilities (if you aren't seeing images but they ARE being created)
Apache doesn't have adequate permissions. Chown the directories to apache's process name, or "chmod -R 777 /new/path" for an insecure quick fix. (Not advised unless you have no other users on your box)
Also, when I check mine (I use a different drive for events), I don't have a trailing slash after the path. Eg
cameras/events
(Which is linked symbolically to a different drive - also works if I specify it directly).
This may be a red herring and ZA is smart enough to strip trailing slashes if not required.
Oh, and when you change Apache's config you need to restart it - in case you didn't. apachectl restart
-
- Posts: 247
- Joined: Sun Jan 16, 2005 11:26 am
As suggested, what is i the apache error_log?
If stuff is getting generated then it must be permissions on apache, and it will be obvious what on from the error_log. Not sure where this will be, but it will be called error_log.
Again, as suggested before it could be permissions on the files. Did you copy them as root and not use the -p option to preserve file permissions i.e. are they now owned by root rather than apache?
If you need to use a larger mountpoint for the events I just mount one up over the top of the apache directory rather than using sym links. Have you tried that?
If stuff is getting generated then it must be permissions on apache, and it will be obvious what on from the error_log. Not sure where this will be, but it will be called error_log.
Again, as suggested before it could be permissions on the files. Did you copy them as root and not use the -p option to preserve file permissions i.e. are they now owned by root rather than apache?
If you need to use a larger mountpoint for the events I just mount one up over the top of the apache directory rather than using sym links. Have you tried that?