SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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.
The web pages are not displaying correctly as it is in the directories every time we updating the directories with new content. I'm not sure we are using mod_cache. How can we tell that mod_cache is being used?
we have suse 10 and apache 2.2
Thanks
I see what you mean. If you're not sure about mod_cache, then you're probably not using it. You can double check with:
# httpd -M
Actually, unless you have evidence to indicate otherwise, I think what you are describing is a client-side issue. Have your user(s) reload their browser, quit/restart their browser, or clear their browser cache if necessary.
With httpd -M command, it says command not found.
Intially we thougt the issue with client side and we cleared temp/cache/restart browser/reboot the system/delete history..but it doesnot help.
Thats the reson I want to see if we can delete cache on apache server if it exists.
It would also be great if can you think of any other thing causing the issue.
Maybe Suse names the Apache web server binary differently. I am not sure.
Could by any (or none) of: # httpd -M # apache -M # apache22 -M
You need to be logged in as root with his full PATH (e.g.: su -) in order for that to work.
It would be a good idea to familiarize yourself with Suse's Apache 2.2 package, and where it keeps various files. Once you have done that, you should begin troubleshooting by watching Apache's access log. Are client requests going to the places you're expecting? etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.