Sponsored Content
Full Discussion: Implementing thread in UNIX
Top Forums UNIX for Advanced & Expert Users Implementing thread in UNIX Post 302609027 by jenanee on Monday 19th of March 2012 07:36:44 AM
Old 03-19-2012
Implementing thread in UNIX

Thanks a lot for this snippet.

I tried one sample program like below:

Code:
 
#!/bin/ksh
date=`date +%y%m%d%H%M%S`
thread() {
echo "test" >> /tmp.txt
echo $date >> /tmp.txt // This to get the time logged for different iterations and see if all processed at same time
}
for i in {1..5}; do
thread &
done

In the output file - i could see the values written only for the 1st iteration but not for the subsequent iteration. Smilie
Does this mean the shell is non-POSIX compliant? or how to test whether it is POSIX compliant and whether it works for the sample script.
Does my sample program makes any sense for testing this functionality and if it is how to confirm that multi-threading is acheived using a sample script?

Last edited by fpmurphy; 03-19-2012 at 11:34 PM.. Reason: code tags please!
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

cliched unix help thread

Windows blows. I'm poor so unix is looking like a great alterative (expecially after my former roommate showed me most of the things it can do). Right now I'm looking at Debian or some other Unix kernel that would run nicley on my computer. But the problem we had with installing it while he was... (3 Replies)
Discussion started by: beardsman
3 Replies

2. Forum Support Area for Unregistered Users & Account Problems

How to post a new thread (Regarding Unix related doubts) in Unix Forums

How to post a new thread (Regarding Unix related doubts) in Unix Forums. I registered my id but I am unable to post my Questions to Forum. Thanks & Regards, indusri (1 Reply)
Discussion started by: indusri
1 Replies

3. UNIX Benchmarks

unix benchmark thread?

Type: UltraSPARC IIIi 1,593 Mhz x2 Ram: 16G Disk: 2*70G fw scsi drives Load: db application kernel: Sunos5.10 pgms: compiled Sun cc -O2 ============================================================== BYTE UNIX Benchmarks (Version 3.11) System -- SunOS sun.spmbox.com 5.10... (2 Replies)
Discussion started by: mr_manny
2 Replies

4. Shell Programming and Scripting

Measure thread execution (in C, unix)

Hi, I have a simulation program which creates two threads and I would like to know if I can measure the time of each individual thread. Threads communicate (I use pthread to manage them) and I want to measure communication time. I found a solution with clock_gettime and CLOCK_THREAD_CPUTIME_ID... (32 Replies)
Discussion started by: Tinkh
32 Replies

5. Shell Programming and Scripting

Read from a file in unix(Continue from previous thread)

Hi This is continuation of previos thread status=running username=abc password=123456 server=linux The script was made which is used to capture the data from file ./scr test status It will give result running I have a case like status = running username=abc password=123456... (14 Replies)
Discussion started by: parthmittal2007
14 Replies

6. Shell Programming and Scripting

What's UNIX Expert's suggestion for this thread ?

Assume that 100 file's of type .txt are saved in directory in which, 40 .txt files having ID 225 in column x 10 .txt files having ID 220 in column x 30 .txt files having ID 115 in column x and remaining 20 .txt file's having UNIQUE ID say 226,227,228,229,230....first I want to read only files... (8 Replies)
Discussion started by: Akshay Hegde
8 Replies

7. Forum Support Area for Unregistered Users & Account Problems

UNIX.com links from Google yield invalid thread error

If one enters a Google search query like site:unix.com mysql php and clicks on the resulting link, one gets the message below: vBulletin Message No Thread specified. If you followed a valid link, please notify the administrator (2 Replies)
Discussion started by: Unregistered
2 Replies
sample(1)						    BSD General Commands Manual 						 sample(1)

NAME
sample -- Profile a process during a time interval SYNOPSIS
sample pid | partial-executable-name [duration [samplingInterval]] [-wait] [-mayDie] [-fullPaths] [-e] [-file filename] DESCRIPTION
sample is a command-line tool for gathering data about the running behavior of a process. It suspends the process at specified intervals (by default, every 1 millisecond), records the call stacks of all threads in the process at that time, then resumes the process. The analysis done by sample is called ``sampling'' because it only checks the state of the program at the sampling points. The analysis may miss execu- tion of some functions that are not executing during one of the samples, but sample still provides useful data about commonly executing func- tions. At the end of the sampling duration, sample produces a report showing which functions were executing during the sampling. The data is con- densed into a call tree, showing the functions seen on the stack and how they were called. (This tree is a subset of the actual call tree for the execution, since some functions may not have been executing during any of the sampling events.) The tree is displayed textually, with called functions indented one level to the right of the callee. In the call tree, if a function calls more than one function then a vertical line is printed to visually connect those separate children functions, making it easier to see which functions are at the same level. The characters used to draw those lines, such as + | : ! are arbi- trary and have no specific meaning. ARGUMENTS
The user of sample specifies a target process (either by process id, or by name), the duration of the sampling run (in seconds), and a sam- pling rate (in milliseconds). If the sampling duration is not specified, a default of 10 seconds is used. Longer sampling durations provide better data by collecting more samples, but could also be confusing if the target process performs many different types of operations during that period. The default sampling rate is 1 millisecond. Fast sampling rates provide more samples and a better chance to capture all the functions that are executing. -wait tells sample to wait for the process specified (usually as a partial name or hint) to exist, then start sampling that process. This option allows you to sample from an application's launch. -mayDie tells sample to immediately grab the location of symbols from the application, on the assumption that the application may exit or crash at any point during the sampling. This ensures that sample can give information about the call stacks even if the process no longer exists. -fullPaths tells sample to show the full path to the source code (rather than just the file name) for any symbol in a binary image for which debug information is available. The full path was the path to the source code when the binary image was built. -e tells sample to open the output in TextEdit automatically when sampling completes. -file filename tells sample the full path to where the output should be written. If this flag is not specified, results are written to a file in /tmp called <application name>_<date>_<time>.<XXXX>.sample.txt, where each 'X' is replaced by a random alphanumeric character. If neither the -e nor -file flags are given, the output gets written to stdout as well as saved to the file in /tmp. SEE ALSO
filtercalltree(1), spindump(8) The Xcode developer tools also include Instruments, a graphical application that can give information similar to that provided by sample. The Time Profiler instrument graphically displays dynamic, real-time CPU sampling information. BSD
Mar. 16, 2013 BSD
All times are GMT -4. The time now is 02:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy