Your computer room will overheat next weekend
11–20 of 24 posts
Re: Your computer room will overheat next weekend
#12This really should be a "duh" for any system administrator. If not, time to find a new job :)
Re: Your computer room will overheat next weekend
#13Air conditioning shuts down on the weekend? THAT'S NOT HOW BUILDING HEAT REGULATION WORKS.
• 4:00pm? Shut it off. Leave the blowers going at least. (Had negotiate life support systems until 6pm in the next lease.)
• Long weekend? Shut it off.
• Compressor that drives the thermostat system fails? Get a cheap household unit from Harbor Freight. (Thunderously loud, ran nearly 24 hours a day, for a while anyway.)
• One of the two main air fans broken? Don't fix. Air still moves. It's ok, I can put on the hearing protection and work in the server room in the afternoons when my west facing office is uninhabitable.
• The remaining fan breaks on Memorial day weekend. Why‽ It was already running 24x7, this is just cruel timing! Now the building gets way too hot and starts transferring heat through the uninsulated walls into my machine room overloading my cooling capacity.
Re: Your computer room will overheat next weekend
#14I wish AMD would hurry the heck up with their 32nm as Intel is too pricey.
Re: Your computer room will overheat next weekend
#15Re: Your computer room will overheat next weekend
#16This really should be a "duh" for any system administrator. If not, time to find a new job :)
Re: Your computer room will overheat next weekend
#17This really should be a "duh" for any system administrator. If not, time to find a new job :)
Re: Your computer room will overheat next weekend
#18Air conditioning shuts down on the weekend? THAT'S NOT HOW BUILDING HEAT REGULATION WORKS.
Re: Your computer room will overheat next weekend
#19This really should be a "duh" for any system administrator. If not, time to find a new job :)
The zillions of little companies with this kind of problem disagree.
Re: Your computer room will overheat next weekend
#20This really should be a "duh" for any system administrator. If not, time to find a new job :)
Unless you work in a large organization, the "system adminstrator" often isn't actually a System Administrator
I can not imagine Google allowing some junior programmer to setup a little closet and run servers in there without contemplating cost, heat/cooling, network allocation, and priviledge management (i.e. what services are running where, why, and who's managing it).
However, the smaller the organization, I can see this happening. 8 man startups without a system administrator... Now that is certainly reality.