Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I think I may have posted this before but the solution only worked termporary.
When I shut down the server, apache tries to resolve all the virtual hosts, for some dumb reason, but since the DNS is turned off before apache, it can't, so it just sits there on each host waiting about 15 minutes or whatever the rediculusly long default tcp time out is. So when you've got a UPS giving you 5 minutes toshut down and the server starts waiting for no reason, it's a big problem. The solution was to make it so DNS stops after apache, but even then, it probably resets itself back to how it was, so it's not a permanent fix. It still does it. Is there a way to stop apachy from doing this? There's no reason why it needs to resolve any hosts, it's shutting down anyway!
Same with when it starts, it does the same, I just want it to start, and I don't care if it can't resove them or not. Once everything is done loading, everything works, and that's what counts. Remote reboots don't seem to cause an issue as I'll sometimes reboot the server and it takes only a few minutes for it to come back. But being able to shut down fast is crucial for my setup.
Edit: It's actually apache2... hmm never knew I got that to work in debian with php, I thought I tried and it did not work. I think it's my evil apt-get update that did that, it also gave me the unstable version of debian, and stuff has been going bad since then.
That line did not do anything, is there a specific place I have to put it? I just sticked it near the start of the file. But the debian apache2 package is messed up, it's all weird and stuff. httpd.conf is just redirecting to apache2.conf, and the virtual hosts are actually all seperate files.
Last edited by Red Squirrel; 08-19-2005 at 09:23 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.