Sponsored Content
Full Discussion: SCO 5.0.6 Media needed
Operating Systems SCO SCO 5.0.6 Media needed Post 302759057 by Scott on Monday 21st of January 2013 10:03:20 AM
Old 01-21-2013
My suggestion would be to create a new thread for this problem.
This User Gave Thanks to Scott For This Post:
 

9 More Discussions You Might Find Interesting

1. SCO

OpenServer 5.0.6 Media Needed

I have a client with 5.0.6 who wants to migrate to new hardware. We have in our posession all appropriate paper software licenses. Over the years the media has vanished Can anyone assist with locating an ISO or actual CD containing OpenServer 5.0.6, please? Thank you (9 Replies)
Discussion started by: theantisco
9 Replies

2. SCO

SCO Unix OpenServer 5.0.5 Media Kit

My client has lost the SCO OS 5.0.5 install media. However, they do have a working SCO 5.0.5 system, but is crumbling apart. Where can I find the SCO OS 5.0.5 install media? Or can I get a copy of the SCO CD as a ISO file? Your help is much appreciated. (7 Replies)
Discussion started by: chedlee88-1
7 Replies

3. SCO

Need installation media for SCO 5.0.4

I need to reinstall SCO 5.0.4 onto another server as the customer does mnot want to pay for another license. Does anoine have the installation media for this? I'm willing to trade as I have every other installation CD. Let me download the 5.0.4 media from you and I'll give you any OS you want. I... (2 Replies)
Discussion started by: buffbiker23
2 Replies

4. SCO

SCO OpenServer 5.0.4 Media Needed

Greetings, I've recently been given responsibility for a legacy server running SCO OpenServer 5.0.4 and upon taking inventory I discovered we have all the license documents but no installation media. Can anyone assist me with where I might download these? Thanks Kevin (9 Replies)
Discussion started by: Kevin Harris
9 Replies

5. SCO

Sco media needed for openserver 5.0.6

Hello, i need if possible media for sco openserver 5.0.6 and also want to know if is possible to upgrade from 5.0.2 to 5.0.6. Best regards, Paolo (1 Reply)
Discussion started by: elnino981
1 Replies

6. SCO

SCO 5.0.2 Installation Media

We recently started having problems with our SCO OpenServer 5.0.2 Server. I know it is VERY outdated but we are unable to move off of it yet due to an application that is still used daily. We have a new software replacement that will be implemented Q3 2016. I was looking for some installation... (0 Replies)
Discussion started by: AOC
0 Replies

7. SCO

Need SCO 5.0.6 openserver media kit

hello everyone i need a copy of sco 5.0.6 iso for isntall a new server crash I read in a post that someone uploaded to an ftp an iso but I did not find the ftp any can helpme? (7 Replies)
Discussion started by: mjgeddo
7 Replies

8. SCO

Need SCO 5.0.5 install media

I need to reinstall SCO Openserver 5.0.5. I have a license, but the install media is long lost. Can anyone help me find an .iso? (12 Replies)
Discussion started by: dudeman411
12 Replies

9. SCO

SCO OpenServer 5.0.6 media needed

My media disk is unusable. Can someone provide me an ISO for Openserver 5.0.6? Thank you. Brantley Allen (2 Replies)
Discussion started by: brantleyallen
2 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)
All times are GMT -4. The time now is 04:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy