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

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Give us your poor, your tired, your huddled Admins... War Stories Post 30646 by Vishnu on Thursday 24th of October 2002 05:29:43 PM

10-24-2002

Registered User

I'm a no administrator (though I'm trying to become one), but I too have a snippet to share...

Right from my college days I was exposed to UNIX systems and even if I was not from comp sci background was attracted to the philosophy of the system as thought of by its designers - Thompson, Ritchi, McIlroy and all...

So when I went to my first job in a consulting company.. I found an atmosphere where my European client had a production and test UNIX boxes which were connected to IBM SNA / CPI-CC to his SAP R/2 production system. I was very happy that I can make use of my UNIX skills. Yes indeed my first assignment was to write automation shell scripts which post/extract EDI messages to/from SAP - UNIX. These scripts used to call C programs using CPI-C interface.

I also learned CPI-C programming, which involves writing your own C code including the CPI-C interface headers and sources - in all there were 8 .C sources and 4 headers, requiring makefiles to do the compilation. There were production C executables doing daily updates and extracts to SAP.

One day I was making some compilation on the test box, while I was monitoring the production box as a privileged user in another terminal. I inadvertently executed a makefile with the same name on the production box which luckily didn't overwrite any existing executable. But my heart stopped thumping, as I had no idea what the script did.. but I had to spend extra hours that day reading the whole script checking for paths and date/time of modifications...

from that day on I was extra careful ascertaining which terminal I'm using for prod/test boxes...

Vishnu

View Public Profile for Vishnu

Find all posts by Vishnu

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 SUSE

pthread_kill

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

NAME

       pthread_kill - send a signal to a thread

SYNOPSIS

       #include <signal.h>

       int pthread_kill(pthread_t thread, int sig);

       Compile and link with -pthread.

DESCRIPTION

       The pthread_kill() function sends the signal sig to thread, another thread in the same process as the caller.  The signal is asynchronously
       directed to thread.

       If sig is 0, then no signal is sent, but error checking is still performed; this can be used to check for the existence of a thread ID.

RETURN VALUE

       On success, pthread_kill() returns 0; on error, it returns an error number, and no signal is sent.

ERRORS

       ESRCH  No thread with the ID thread could be found.

       EINVAL An invalid signal was specified.

CONFORMING TO

       POSIX.1-2001.

NOTES

       Signal dispositions are process-wide: if a signal handler is installed, the handler will be invoked in the thread thread, but if the dispo-
       sition of the signal is "stop", "continue", or "terminate", this action will affect the whole process.

SEE ALSO

       kill(2) sigaction(2), sigpending(2), pthread_self(3), pthread_sigmask(3), raise(3), pthreads(7), signal(7)

COLOPHON

       This  page is part of release 3.25 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								    2009-01-28							   PTHREAD_KILL(3)