please help (closed homework thread) Post: 50796

4 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

my thread got closed

I had a thread open and now it says it's closed. I had a question still on the forum and about 15mins after I posted my most recent question on it the thread said "closed". Why did this happen? I didn't violate any forum rules. Is there a limit on how many postings you can have in a single thread?...

2. Post Here to Contact Site Administrators and Moderators

Thread closed when learner has tried

I'm not so sure that this thread should have been closed. Though it was clearly homework the student was asking a specific question related to the assignment, but not the answer to the whole assignment. /www.unix.com/unix-dummies-questions-answers/107494-how-get-rid.html . IMHO The solution is...

3. UNIX for Dummies Questions & Answers

3 homework questions (thread closed)

1st) how can i print only directories? 2nd) how can i print files that someone used in the last X days (for example, 5). thanks very much, i need it for homework and teacher teachs us nothing:(

4. Solaris

Interview questions [thread closed]

Hi all, i have found a set questions from the net, i thought it will be great to ask and share with you gurus. I have the questions and some answers (correct me, if i am wrong) for these set of questions. 1. What file do you modify to change the mail aliases (Provide the full path) ? Ans:...

LEARN ABOUT LINUX

thread-keyring

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)