Omega Owners Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Please check the Forum Guidelines at the top of the Newbie section

Pages: [1]   Go Down

Author Topic: Jim has fixed it  (Read 951 times)

0 Members and 1 Guest are viewing this topic.

Taxi_Driver

  • Guest
Jim has fixed it
« on: 02 July 2007, 18:45:53 »
Or rather TB  ;D :y
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107016
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Jim has fixed it
« Reply #1 on: 02 July 2007, 18:52:30 »
Quote
Or rather TB  ;D :y
Up now, may have to go through another reboot once I've investigated further.
Logged
Grumpy old man

Bo Bo

  • Omega Baron
  • *****
  • Offline Offline
  • Gender: Male
  • Coventry
  • Posts: 4812
  • Here's another nice mess you've gotten me into!
    • View Profile
Re: Jim has fixed it
« Reply #2 on: 02 July 2007, 19:03:06 »
Quote
Quote
Or rather TB  ;D :y
Up now, may have to go through another reboot once I've investigated further.
Was wondering.....
Logged
Where would we be without rhetorical questions?!

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107016
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Jim has fixed it
« Reply #3 on: 02 July 2007, 21:32:12 »
We've been working on this all evening.  Although we think we know how it happened, we do not yet fully understand why it happened.  End result is Apache threw a strop, most likely due to the weaknesses in Linux kernel's memory management.  Why the kernel struggled to manage the situation, and what caused the situation to develop is still being looked at.

Apologies for the inconvenience.
Logged
Grumpy old man

Jay w

  • Omega Baron
  • *****
  • Offline Offline
  • Gender: Male
  • Plymouth/Poole
  • Posts: 4319
  • omega gone
    • View Profile
Re: Jim has fixed it
« Reply #4 on: 02 July 2007, 22:30:13 »
Quote
We've been working on this all evening.  Although we think we know how it happened, we do not yet fully understand why it happened.  End result is Apache threw a strop, most likely due to the weaknesses in Linux kernel's memory management.  Why the kernel struggled to manage the situation, and what caused the situation to develop is still being looked at.

Apologies for the inconvenience.


there are words on the screen, i have tried to read them out aloud, still it doesn't make sense......

Never mind....is the forum still working??? yes.....the technical side i will leave to the technical guys  :y
Logged

TheBoy

  • Administrator
  • *****
  • Offline Offline
  • Gender: Male
  • Brackley, Northants
  • Posts: 107016
  • I Like Lockdown
    • Whatever Starts
    • View Profile
Re: Jim has fixed it
« Reply #5 on: 02 July 2007, 22:35:59 »
Quote
Quote
We've been working on this all evening.  Although we think we know how it happened, we do not yet fully understand why it happened.  End result is Apache threw a strop, most likely due to the weaknesses in Linux kernel's memory management.  Why the kernel struggled to manage the situation, and what caused the situation to develop is still being looked at.

Apologies for the inconvenience.


there are words on the screen, i have tried to read them out aloud, still it doesn't make sense......

Never mind....is the forum still working??? yes.....the technical side i will leave to the technical guys  :y
Sorry, for those who are not that way inclined, it broke around 6pm, took about 35mins to fix.

Posted a little techie stuff to satisfy those who do like to know what broke.
Logged
Grumpy old man
Pages: [1]   Go Up
« previous next »
 

Page created in 1.57 seconds with 21 queries.