httpd restarted cuts off downloads?

young

Verified User
Joined
Oct 22, 2003
Messages
77
is there any way to restart httpd without cutting off downloads since httpd restarts now every night at around 12:12:01am? or is there a way to not restart httpd every night. or to restart httpd when no one is downloading.
 
Hmm so have I got this right?

When the tally runs, it rotates logs and in turn it restarts apache?

I am amazed noone has complained to me, if apache indeed is been restarted every night.
 
It's likely apache has been restarted every night.

I don't really know if that will stop a download because I don't know if the pointer (or state) information is kept in the browser or in apache.

Anyone else know?

Jeff
 
jlasman said:
It's likely apache has been restarted every night.

I don't really know if that will stop a download because I don't know if the pointer (or state) information is kept in the browser or in apache.

Anyone else know?

Jeff
i tried watching a wmv on a webpage and restarted apache while the wmv was downloading. the wmv got cut off at about 9% download.
 
Thanks for the info.

I believe it would have to be a huge coincidence for someone to be downloading a large file (as opposed to just a webpage) when Apache is restarted.

Nevertheless it could happen on any server, not just a shared server. I believe we have to live with it. If you think there might be an answer, I'd love to hear it.

That said, Plesk servers shut down httpd completely (and other services as well) for the entire time it takes for them to run their backup.

Jeff
 
I think in this case its bad apache design, other apps usually need just whats called a rehash to update configuration and rotate logs, apache is unusual that it needs a restart.
 
Do you know for a fact it needs a restart? It might just need a reload.

I think the best place to ask would probably be on an apache users forum.

Jeff
 
Well I dont know if every single config change needs a restart but I know vhost changes need a restart, most changes done on apache are vhost changes the rest is usually just setup once on initial setup.

Mod_security changes need a restart, php.ini changes need a restart. I would guess a lot more stuff requires a restart as well.
 
Back
Top