Sponsored Content
Full Discussion: Help with hijacked thread
Contact Us Post Here to Contact Site Administrators and Moderators Help with hijacked thread Post 302807397 by Don Cragun on Tuesday 14th of May 2013 03:41:26 PM
Old 05-14-2013
Help with hijacked thread

A recent post is hijacking a thread on a completely unrelated topic. Any help you can provide in moving this posting to a new thread (or at least removing it from the current thread) would be greatly appreciated.

Thanks,
Don
 

3 More Discussions You Might Find Interesting

1. Programming

How to cancel a thread safely from the initial thread?

how about asynchronous canceling? or with signal? if with signal whether it effects the process? my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies

2. Programming

Parent Thread Of Child Thread

Parent Thread Of Child Thread Suppose a process creates some threads say threadC and threadD. Later on each of these threads create new child threads say threadC1, threadC2, threadC3 etc. So a tree of threads will get created. Is there any way to find out the parent thread of one such... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

3. UNIX and Linux Applications

Check out Multiple Hijacked Files in Clearcase

How can we checkout multiple hijacked files in Clearcase? I need to find hijacked files recursively in a snapshot view & check those out. I tried to use the command: cleartool co -nc `cleartool ls -recurse | grep "hijacked" | sed s/\@\@.*// | xargs` but it gives me an error: cleartool:... (2 Replies)
Discussion started by: anjalim6
2 Replies
THREAD-KEYRING(7)					     Linux Programmer's Manual						 THREAD-KEYRING(7)

NAME
thread-keyring - per-thread keyring DESCRIPTION
The thread keyring is a keyring used to anchor keys on behalf of a process. It is created only when a thread requests it. The thread keyring has the name (description) _tid. A special serial number value, KEY_SPEC_THREAD_KEYRING, is defined that can be used in lieu of the actual serial number of the calling thread's thread keyring. From the keyctl(1) utility, '@t' can be used instead of a numeric key ID in much the same way, but as keyctl(1) is a program run after forking, this is of no utility. Thread keyrings are not inherited across clone(2) and fork(2) and are cleared by execve(2). A thread keyring is destroyed when the thread that refers to it terminates. Initially, a thread does not have a thread keyring. If a thread doesn't have a thread keyring when it is accessed, then it will be created if it is to be modified; otherwise the operation fails with the error ENOKEY. SEE ALSO
keyctl(1), keyctl(3), keyrings(7), persistent-keyring(7), process-keyring(7), session-keyring(7), user-keyring(7), user-session-keyring(7) Linux 2017-03-13 THREAD-KEYRING(7)
All times are GMT -4. The time now is 07:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy