Sponsored Content
Top Forums Programming pthread_create fails when used with pthread_attr_setinheritsched() on HPUX Post 302103209 by jeet_xp on Wednesday 17th of January 2007 04:24:40 AM
Old 01-17-2007
NAME
rtsched - execute process with real-time priority

SYNOPSIS
rtsched -s scheduler -p priority command [arguments]

rtsched [ -s scheduler ] -p priority -P pid

DESCRIPTION
Rtsched executes command with POSIX or HP-UX real-time priority, or
changes the real-time priority of currently executing process pid.
----------------------------------------------------------------------------

this is what I found when I checked the man page of the rtsched. This basically tells about the process scheduling on HP-UX.
And my program illustrated above only playing with the standard pthreads.
Can you put more focus on this.
I did not get what you wanted to suggest.
Please respond and correct me if I am wrong here.
 

10 More Discussions You Might Find Interesting

1. Programming

pthread_create problem

Here is simple code for multithreading in POSIX: void* simplethread(void* arg) { printf("Hello World\n"); } int main(void) { pthread_t id; pthread_create(&id, NULL, simplethread, NULL); return 0; } Whether the new thread will run or not depends on the OS. Tricky ... (5 Replies)
Discussion started by: _rocky
5 Replies

2. Programming

unresolve pthread_create etc

how to do with that? after cc -o xxxx xxxx.c ld: Unresolved: _pthread_create _pthread_deteach _pthread_exit Thanks (3 Replies)
Discussion started by: zhshqzyc
3 Replies

3. Programming

pthread_create and scope usage

I have a problem with a C multi-threaded program I am writing. I cannot figure out how to keep the unique key value at the thread level. I wrote a program in C that forked a bunch of processes and then decided to convert it to threads and I can't keep the key unique to each thread. In a nutshell... (3 Replies)
Discussion started by: jenmead
3 Replies

4. Programming

Pthread_create issue

Hello My problem goes like this: I have used Pthread_create, and I have tryed to create 2 proccess but nothing happens! It does not even matter what the function im trying to create do. It is if im trying to activate an empty function. This is my code. Any help will be highly appreciated.... (1 Reply)
Discussion started by: Hellboy
1 Replies

5. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

6. Programming

How Can I use pthread_create ?

Hi. I use C++ and I wishes to create a thread with the pthread_create function, my question is, how can I do this if I wish that the function will be a member of the class ?? I know from windows programming that I can declare a static function like this static unsigned int __stdcall... (7 Replies)
Discussion started by: shvalb
7 Replies

7. Programming

pthread_create

The prototype for pthread_create function is like this:- int pthread_create(pthread_t *thread,pthread_attr_t *attr,void *(*start routine),void *arg); Q.1 .Why the return type of the start_routine must be void*?? Q.2. Why should we pass arg by converting into void * only ?? Thank You (3 Replies)
Discussion started by: sunil_abhay
3 Replies

8. UNIX for Dummies Questions & Answers

Pthread_create problem

Hi, I'm trying to do my homework assignment but I am having trouble using the pthread_create fucntion. Here is my code________________ //Alicia Johnson //sum_pid program //creates n number of threads. These threads create a random number //then adds the number to a global array. Then... (1 Reply)
Discussion started by: ajohns38
1 Replies

9. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies

10. Programming

fork vs pthread_create

Suppose I have a simple program main() with a global varibale int x=0. int x = 0; main() { print("%d\n",x); } I want to create two threads/process which must access this variable x in sync. Which one will be better threads( pthread_create ) or process( fork )? If I go with fork() then... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
rtsched(1)						      General Commands Manual							rtsched(1)

NAME
rtsched - execute process/lightweight process (LWP) with real-time priority SYNOPSIS
scheduler priority command [arguments] scheduler] priority scheduler] priority scheduler] priority DESCRIPTION
executes command with POSIX or HP-UX real-time priority, or changes the real-time priority of currently executing process (pid) or light- weight process (lwpid). All POSIX real-time priority processes or LWPs are of greater scheduling importance than processes/LWPs with HP-UX real-time or HP-UX time- share priority. All HP-UX real-time priority processes/LWPs are of greater scheduling importance than HP-UX timeshare priority pro- cesses/LWPs, but are of lesser importance than POSIX real-time processes/LWPs. Neither POSIX nor HP-UX real-time processes/LWPs are subject to degradation. POSIX real-time processes/LWPs may be scheduled with one of three different POSIX real-time schedulers: SCHED_FIFO, SCHED_RR, or SCHED_RR2. See rtsched(2) for details. is a superset of See rtprio(1). Options Specify the desired scheduler: POSIX real-time schedulers: SCHED_FIFO SCHED_RR SCHED_RR2 HP-UX real-time scheduler: SCHED_RTPRIO HP-UX timeshare scheduler: SCHED_HPUX SCHED_NOAGE Specify priority range; any integer within the inclusive priority range of the corresponding scheduler. is required for all schedulers except SCHED_HPUX. If scheduler is SCHED_HPUX, the priority argument is ignored. The default priority range of each scheduler is as follows: scheduler highest priority lowest priority -------------------------------------------------- SCHED_FIFO 31 0 SCHED_RR 31 0 SCHED_RR2 31 0 SCHED_RTPRIO 0 127 SCHED_NOAGE 178 255 SCHED_HPUX N/A N/A Higher numerical values for the priority represent higher priorities under POSIX real-time schedulers, whereas lower numeri- cal values for the priority represent higher priorities under HP-UX real-time and timeshare schedulers. Specify an already executing process ID (pid). Specify an already executing lightweight process ID (lwpid). The target LWP (lwpid) can be in any process. Select all the LWPs in an already executing process (specified with When scheduling policy is not specified explicitly using the option, the process's current schedul- ing policy will be used. If the requested priority value is in the range for this scheduling policy, the scheduling policy and priority of the process and all its LWPs will be changed to these values. Please note that it may cause the scheduling policy to be changed for some LWPs. If the user is not a member of a group having access and is not the user with appropriate privileges, command is not scheduled, or pid's/ lwpid's real-time priority is not changed. When changing the real-time priority of a currently executing process/LWP, the effective user ID of the calling process must be the user with appropriate privileges, or the real or effective user ID must match the real or saved user ID of the process to be modified. In presence of processor sets (see pset_create(2) for details), the application execution is restricted to processors in the application's processor set. The threads in different processor sets do not compete with one another for processors based on their scheduling policy and priority values. The scheduler looks only at threads assigned to a processor's processor set to choose the next thread to run. RETURN VALUE
returns exit status: if command is successfully scheduled or if pid's or lwpid's real-time priority is successfully changed; if command is not executable, pid or lwpid does not exist, or priority is not within the priority range for the corresponding scheduler; if command (pid/lwpid) lacks real-time capability, or the invoker's effective user ID is not a user who has appropriate privi- leges, or the real or effective user or the real or effective user ID does not match the real or saved user ID of the process being changed; or if rtsched encountered an internal error or if rtsched is not supported by this release. EXAMPLES
Execute file with SCHED_FIFO at a priority of 10: Execute file with SCHED_RTPRIO at a priority of 127 (this is synonymous to Execute file with the SCHED_HPUX scheduler: This is useful to spawn a timeshare priority command from a real-time priority shell. Set the currently running process, pid 24217, to execute with SCHED_RR2 at a priority of 20: Now change its priority to 10 using the same scheduler: Set the currently running LWP, lwpid 987312, to execute with SCHED_RR at a priority of 10: Set all currently executing LWPs in a process pid 21342 to execute with SCHED_FIFO at a priority of 25: WARNINGS
The priority values used by may differ from those used by other commands. For example, ps(1) displays the internal representation of pri- ority values. AUTHOR
was developed by HP. SEE ALSO
rtprio(1), setprivgrp(1M), getprivgrp(2), pset_create(2), rtprio(2), rtsched(2), _lwp_getscheduler(2), _lwp_setscheduler(2), pstat_getlwp(2). rtsched(1)
All times are GMT -4. The time now is 08:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy