From 558c08c358c16c8a2ddadc3ac03935fce0b2e895 Mon Sep 17 00:00:00 2001 From: Julian Elischer Date: Tue, 12 Dec 2006 08:13:02 +0000 Subject: [PATCH] Remove reference to confusing behaviour just removed from the kse_exit() syscall. Describe the correct behaviour. --- lib/libc/sys/kse.2 | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/lib/libc/sys/kse.2 b/lib/libc/sys/kse.2 index b6adba1819ce..340c7a0beb16 100644 --- a/lib/libc/sys/kse.2 +++ b/lib/libc/sys/kse.2 @@ -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 threads associated with the KSE group blocked in the kernel. This system call does not return unless there is an error. -.Pp -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 +Calling .Fn kse_exit -returns normally. -This returns the process to its original, unthreaded state. +from the last thread is the same as calling +.Fn exit . .Pp The .Fn kse_release