d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove reference to confusing behaviour just removed from

Browse Source 
the kse_exit() syscall. Describe the correct behaviour.
This commit is contained in:
Julian Elischer 2006-12-12 08:13:02 +00:00
parent 0c17ece676
commit 558c08c358
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
lib/libc/sys/kse.2
View File

@ -264,13 +264,10 @@ causes the KSE assigned to the currently running thread to be destroyed.
If this KSE is the last one in the KSE group, there must be no remaining If this KSE is the last one in the KSE group, there must be no remaining
threads associated with the KSE group blocked in the kernel. threads associated with the KSE group blocked in the kernel.
This system call does not return unless there is an error. This system call does not return unless there is an error.
.Pp Calling
As a special case, if the last remaining KSE in the last remaining KSE group
invokes this system call, then the KSE is not destroyed;
instead, the KSE just loses the association with its mailbox and
.Fn kse_exit .Fn kse_exit
returns normally. from the last thread is the same as calling
This returns the process to its original, unthreaded state. .Fn exit .
.Pp .Pp
The The
.Fn kse_release .Fn kse_release