Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Isn't it just saying that it can't find the mods-enabled directory?
No, it's saying that it can't find
/var/www/mods-enabled
probably because mods-enabled folder resides in
/etc/apache2/mods-enabled
or have you moved that into the default document root of the server?
That's a kind of "windows approach": unnecessary and besides you don't learn anything from it.
*What I do is put system and daemon configuration under revision control (any should work from good 'ol RCS to HG or whatever you're comfortable with). Yes, it requires the discipline to (remember) use it (I use a wrapper around vi) and make appropriate comments before committing but it means that 0) you're able to see when a change was made, 1) what the change contains and 2) roll back changes more easily for debugging / testing / SNAFU purposes.
Doing that (or making backups) would have allowed you to see you fscked up your config yourself:
Quote:
Originally Posted by sniper8752
Code:
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"
# Modified by me!
ServerRoot /var/www
Sorry, a little to confusing for me. I am still learning Apache, and am lost. I reviewed what you highlighted in red, and so I commented out the ServerRoot line. Was this the right thing to do? I also did the following (uncommented this line as well and removed the "'s):
ServerRoot /etc/apache2
Last edited by sniper8752; 05-07-2013 at 03:54 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
