Give us your poor, your tired, your huddled Admins... War Stories Post: 30703

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Give us your poor, your tired, your huddled Admins... War Stories Post 30703 by RTM on Friday 25th of October 2002 11:11:54 AM

10-25-2002

Registered User

I've got two great ones done by the same person - an Engineer working in a hospital.

One - problem with A/C units drain pipe clogging and backing up under the data center floor and shorting out data cables due to corrosion.

Solution - put bricks under the cables.

Problem with solution - he never thought that the water could get so high to go beyond the bricks - and never put bricks under the electrical cables. Problem with draining happened again and fortunately was discovered before major electrical problems. Water reached 3/4 of the way up the bricks. Almost topped the electrial outlets (flat outlets on floor maybe 3 inches high) Engineer was not allowed in D-C without escort.

Two: Same engineer brought back in for water problem. He contacted a company that makes Hog socks. They are suppose to be used for containing oil/hydraulic spills in shops. He figured they would soak up water too. He was escorted into the D-C and started placing these 'socks' around the computer electrical outlets. They were near or in front of the A/C blower and the constant blowing caused the material inside the socks to be blow out. It was ground corn husk which looked like fairy dust in the cartoons. The stuff was all over the place and the two escorts and the Engineer didn't notice it. I walked into the D-C and noticed this gold dust everywhere! I went beserk and threw the guy out, started collecting up the hog socks and tossing them out the door. We had to bring in an Enviromental team from Digital to check out our servers. Remember, this is in a hospital where we are suppose to be up 24X7, 365 days a year. We were down 2 days, lost something like 5 hard drives. There is still some dust under the floor if you look under cables. My old boss has a small glass container of the 'fairy dust' sitting on his desk to remind him to never trust the guy. Water problem was addressed by others (water sensor/alarm installed - second drain installed ) The company who makes those hog socks was contacted - they told us these things are not made for computer environments and that the Engineer never mentioned what he was using them for.

RTM

View Public Profile for RTM

Find all posts by RTM

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

regexp: really tired, guru help needed...

Hello all! Please help me with the following complex regexp which works in egrep: egrep '\"http:\/\/ccc\.bbb\.com\/documents\/0000\/{4}\/(+\.{3})*\"' my-file.htmlBut silently does not work in sed: sed "s/\"http:\/\/ccc\.bbb\.com\/documents\/0000\/{4}\/(+\.{3})*\"/aaa/g" my-file.htmlor sed...

2. AIX

Poor Performance of server

Hi, I am new registered user here in this UNIX forums. I am a new system administrator for AIX 6.1. One of our servers performs poorly every time our application (FINACLE) runs many processes/instances. (see below for topas snapshot) I use NMON or Topas to monitor the server utilization. I...

LEARN ABOUT LINUX

pthread_detach

PTHREAD_DETACH(3)					     Linux Programmer's Manual						 PTHREAD_DETACH(3)

NAME

       pthread_detach - detach a thread

SYNOPSIS

       #include <pthread.h>

       int pthread_detach(pthread_t thread);

       Compile and link with -pthread.

DESCRIPTION

       The  pthread_detach()  function	marks  the  thread identified by thread as detached.  When a detached thread terminates, its resources are
       automatically released back to the system without the need for another thread to join with the terminated thread.

       Attempting to detach an already detached thread results in unspecified behavior.

RETURN VALUE

       On success, pthread_detach() returns 0; on error, it returns an error number.

ERRORS

       EINVAL thread is not a joinable thread.

       ESRCH  No thread with the ID thread could be found.

CONFORMING TO

       POSIX.1-2001.

NOTES

       Once a thread has been detached, it can't be joined with pthread_join(3) or be made joinable again.

       A new thread can be created in a detached state using pthread_attr_setdetachstate(3) to set the detached attribute of the attr argument	of
       pthread_create(3).

       The  detached  attribute merely determines the behavior of the system when the thread terminates; it does not prevent the thread from being
       terminated if the process terminates using exit(3) (or equivalently, if the main thread returns).

       Either pthread_join(3) or pthread_detach() should be called for each thread that an application creates, so that system resources  for  the
       thread can be released.	(But note that the resources of all threads are freed when the process terminates.)

EXAMPLE

       The following statement detaches the calling thread:

	   pthread_detach(pthread_self());

SEE ALSO

       pthread_attr_setdetachstate(3), pthread_cancel(3), pthread_create(3), pthread_exit(3), pthread_join(3), pthreads(7)

COLOPHON

       This  page is part of release 3.27 of the Linux man-pages project.  A description of the project, and information about reporting bugs, can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2008-11-27							 PTHREAD_DETACH(3)