506 reputation
36
bio website linkedin.com/in/robwells57
location London, United Kingdom
age 57
visits member for 5 years, 6 months
seen Jul 31 at 12:52

An Aussie currently located in Maidenhead in the UK. I'm proud to have lived and worked in France, Germany, Ireland, Norway and Australia.

Currently working on developing for and supporting the platform for a really big media website.

Really, really big website!


Jan
2
awarded  Good Answer
Oct
18
awarded  Tumbleweed
Sep
24
awarded  Yearling
May
22
awarded  Nice Answer
May
1
awarded  Yearling
Dec
12
comment Side effects of an Apache2 Reload event
Hmmm. I wonder if you're confusing Apache reloads after modifying the Apache config with what you need to do after modifying the content being served? </obvious> Just thought I'd ask.
Dec
12
comment Side effects of an Apache2 Reload event
BTW "It Works!!!" (-: (Just had a peek)
Dec
12
comment Side effects of an Apache2 Reload event
... (ran out of space). Regularly HUP'ing your site will cause service disruption and you are better off attempting a graceful restart. But I'd take a look at how often you are expecting to modify configs and then come up with your restart frequency from there. What sort of load are your servers under?
Dec
12
comment Side effects of an Apache2 Reload event
G'day, we've found that we were getting some strange behaviour using the graceful|restart option. Primarily that some child processes were left hanging around. Sometimes as zombies. My undertanding is that doing a HUP will force an immediate shutdown and reload, i.e. it is not graceful. I am actually playing with this at the moment. The new "||" syntax for logging will enable us to rotate our logs nightly without having to HUP the Apache servers and have them just drop connections which is currently a problem with large downloads of programmes for a certain major UK streaming service. ;-)
Dec
12
answered Side effects of an Apache2 Reload event
Aug
18
answered Moving an already-running process to Screen
Aug
10
comment Can someone tell me if this is a plausible apache concern?
@SpaceManSpiff, you are totally correct. It needs to be captured and secured in a better way. @Justin, you are also totally correct in that it is a storage and performance killer. Both of which we are trying to address at the moment for one of the major web sites in the world that I happen to be involved with. Possibly using centralised logging. BTW The web site involved has 400,000+ updates per day and peak hit rates of millions of hits per second for more than an hour!
Aug
7
awarded  Editor
Aug
7
revised Can someone tell me if this is a plausible apache concern?
Fixed crap grammer and added small note
Aug
7
comment Can someone tell me if this is a plausible apache concern?
@tvanfosson, we've seen lots of problems where httpd's don't shutdown gracefully to the point where we currently have to HUP the server nightly as a part of our log rotation effort.
Aug
7
comment Can someone tell me if this is a plausible apache concern?
@Justin, it could be a big deal if you have auditing and archiving requirements that you have to legally comply with.
Aug
7
answered Can someone tell me if this is a plausible apache concern?
Jul
16
awarded  Teacher
Jul
16
answered linux: kill all my processes but not this terminal
Apr
30
awarded  Supporter