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
Old 10-24-2002
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...
 

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... (7 Replies)
Discussion started by: ulrith
7 Replies

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... (9 Replies)
Discussion started by: guzzelle
9 Replies
PTHREAD_SELF(3) 					     Linux Programmer's Manual						   PTHREAD_SELF(3)

NAME
pthread_self - obtain ID of the calling thread SYNOPSIS
#include <pthread.h> pthread_t pthread_self(void); Compile and link with -pthread. DESCRIPTION
The pthread_self() function returns the ID of the calling thread. This is the same value that is returned in *thread in the pthread_cre- ate(3) call that created this thread. RETURN VALUE
This function always succeeds, returning the calling thread's ID. ERRORS
This function always succeeds. CONFORMING TO
POSIX.1-2001. NOTES
POSIX.1 allows an implementation wide freedom in choosing the type used to represent a thread ID; for example, representation using either an arithmetic type or a structure is permitted. Therefore, variables of type pthread_t can't portably be compared using the C equality operator (==); use pthread_equal(3) instead. Thread identifiers should be considered opaque: any attempt to use a thread ID other than in pthreads calls is nonportable and can lead to unspecified results. Thread IDs are only guaranteed to be unique within a process. A thread ID may be reused after a terminated thread has been joined, or a detached thread has terminated. The thread ID returned by pthread_self() is not the same thing as the kernel thread ID returned by a call to gettid(2). SEE ALSO
pthread_create(3), pthread_equal(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-10-24 PTHREAD_SELF(3)
All times are GMT -4. The time now is 02:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy