9 More Discussions You Might Find Interesting
1. AIX
Hello, AIX 7.1 - several NetApp disks already running. Trying to install a new one. Storage folks provision it. I run cfgmgr - nothing. no new disks show up in "lsdev", "sanlun lun show" shows no new device. No errors, just nothing. Storage guys disconnect it and attaches to another aix server -... (5 Replies)
Discussion started by: sid
5 Replies
2. HP-UX
Hi All ,
Here we have 1 physical machine followed by 5 guest machine under HPVM.
Version HPVM -- B.04.20 -- Integrity VM HPVM
The main role of the base machine is to serve all the guest machine .
What is the best procedure to restart all the host and guest ... (0 Replies)
Discussion started by: marunmeera
0 Replies
3. Shell Programming and Scripting
Hi gurus,
I hit a block when write the script.
I need do while loop, in the loop I have code below.
sqlplus -s abc/abc@abc <<EOF
spool testwhile
select *
from dual;
spool off
exit;
EOF
when I run script with only this code, it works fine.
if I add code as below:
#!/bin/ksh
... (5 Replies)
Discussion started by: ken6503
5 Replies
4. Shell Programming and Scripting
Hi all,
I have some sections of a script that I am trying to add error handling to. Basically if it returns any error, just continue. This is for a deployment script that i am writing to assist in the deployment of scripts out to other systems.
At the top of my KSH script i added this... (5 Replies)
Discussion started by: nitrobass24
5 Replies
5. UNIX for Dummies Questions & Answers
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies
6. HP-UX
Hi All,
There are few threads regarding this subject of being unable to create more guests due to lack of RAM. So I am aware how the sum works.. add 8.5% to whatever is allocated, be that the host or guest. But I'm not sure if I have a hardware issue with memory or what I see is correct as I am... (3 Replies)
Discussion started by: EricF
3 Replies
7. Shell Programming and Scripting
How can you efficiently add pairs of files together and then paste those pairs,
I have a climate computer at work which spits out temperatures and stuff out twice a day, one for the day-data and one for the night (basically). Every week I want to make a nice overview
The text files are... (1 Reply)
Discussion started by: uwgandalf
1 Replies
8. Virtualization and Cloud Computing
1. Can somebody tell me the log file location of HPVM where all the events of guest OS are reported ?
2. And if possible a log file with important events in it ? (1 Reply)
Discussion started by: thegeek
1 Replies
9. Red Hat
Hi Guys,
as above, how do I enable automount for USB/CDROM/DVDROM in RHEL4 & 5?
I have searched the forum on this topic but didn't find any.
Also searched the net but it seems confusing and there are different ways to do things depending on the distros.
Btw, I am on RHEL command line only... (4 Replies)
Discussion started by: DrivesMeCrazy
4 Replies
pthread_key_create(3T) pthread_key_create(3T)
NAME
pthread_key_create(), pthread_key_delete() - create or delete a thread-specific data key
SYNOPSIS
PARAMETERS
key This is either a pointer to the location where the new key value will to be returned (create function) or the thread-spe-
cific data key to be deleted (delete function).
destructor
Function to be called to destroy a data value associated with key when the thread terminates.
DESCRIPTION
creates a unique thread-specific data key. The key may be used by threads within the process to maintain thread-specific data. The same
key is used by all threads, but each thread has its own thread-specific value associated with key. For each thread, the value associated
with key persists for the life of the thread.
By default, the system allows a process to create up to number of thread-specific data keys. If the process needs more keys, the environ-
ment variable can set the number of keys up to a maximum of 16384. If a value outside the range of and 16384 is specified, or if the envi-
ronment variable is not set at all, the default value is considered. When a new thread-specific data key is created, each thread will ini-
tially have the value NULL associated with the new key. Each time a thread is created, the new thread will have the value NULL for each
thread-specific data key that has been created in the process. A thread may use to change the value associated with a thread-specific data
key. Note: is an opaque data type.
When a thread terminates, it may have non-NULL values associated with some or all of its thread-specific data keys. Typically, these val-
ues will be pointers to dynamically allocated memory. If this memory is not released when the thread terminates, memory leaks in the
process occur. An optional function may be provided at key creation time to destroy the thread-specific data of a terminating thread.
When a thread terminates, the thread-specific data values associated with the thread will be examined. For each key that has a non-NULL
thread-specific data value and a destructor function, the destructor function will be called with the thread-specific data value as its
sole argument. The order in which destructor functions are called is unspecified.
Once all the destructor functions have been called, the thread-specific data values for the terminating thread are examined again. If
there are still non-NULL values in which the associated keys have destructor functions, the process of calling destructor functions is
repeated. If after iterations of this loop there are still some non-NULL values with associated destructors, the system may stop calling
the destructors or continue calling the destructors until there are no non-NULL values. Note: This may result in an infinite loop.
If a destructor function is not desired for key, the value NULL may be passed in the destructor parameter.
The function deletes a thread-specific data key. The key must have been previously created by The thread-specific data values associated
with key are not required to be NULL when this function is called. Using key after it has been deleted results in undefined behavior.
If a destructor function is associated with key, it will not be invoked by the function. Once key has been deleted, any function that was
associated with key is not called when a thread exits. It is the responsibility of the application to free any application storage for
each of the threads using key.
The function can be called from a destructor function.
RETURN VALUE
If successful, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
If any of the following occur, the function returns the corresponding error number:
The value specified by
key is invalid.
The necessary resources to create another thread-specific
data key are not available, or the total number of keys per process has exceeded or an invalid value was specified
with the environment variable
There is insufficient memory available in which to create
key.
For each of the following conditions, if the condition is detected, the function returns the corresponding error number:
The value specified by
key is invalid.
AUTHOR
and were derived from the IEEE POSIX P1003.1c standard.
SEE ALSO
pthread_getspecific(3T), pthread_setspecific(3T).
STANDARDS CONFORMANCE
Pthread Library pthread_key_create(3T)