I wrote this code, questions follow
#! /bin/bash -f
# Purpose - to show how if syntax is used within an awk
clear;
ls -l;
echo "This will print out the first two columns of the inputted file in this directory";
echo "Enter filename found in this directory";
read input;
... (11 Replies)
Heyas
I'm trying to build a live image using livecd-tools (livecd-creator), but this time i'd like to reuse the /root/anaconda-ks.cfg.
System: Fedora 3.16.7-200.fc20.x86_64
The building starts, the download begins, but it fails with networking.
MAIN.ks
# Based on: fedora-live-base.ks... (0 Replies)
Hi,
I am trying to check if two input files exist before the rest of the scripts is run. Following is the code that I have but it gives me syntax error.
if
then
echo "File not found"
else
echo "File found"
fi (3 Replies)
i have automated installation of my proprietory linux.. using PXE. it all goes well. but after complete installation, while using the admin interface.. i am facing display problems.
is it due to package dependencies.?
or i have to write post script in anaconda-ks.cfg file???
can some one tell... (10 Replies)
i create ks.cfg for automatic install for centos 5.2 it's work perfectky for cutom install linux package.
and i want to install another program with shell scripts (assume test.tar include in DVD linux custom package)** single dvd include linux os and test.tar
sample
#!/bin/bash... (1 Reply)
Hi Folks,
I am trying to write a small compiler for syntax checking in C programs. I would like to attach a Context Free Grammar(CFC) to it.
Does any one know as to how I should associate or map the Grammar with the C program????
A quick help would help me a lot......
Thanks,
Nisha (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)
10-07-2009
Wrong Post