All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Rahul Bedarkar <rahulbedarkar89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC PATCH 1/1] pthread_detach.3: remove invalid and confusing statement
Date: Thu, 08 Oct 2015 23:10:12 +0200	[thread overview]
Message-ID: <5616DBB4.7060903@gmail.com> (raw)
In-Reply-To: <1443247457-3507-1-git-send-email-rahulbedarkar89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Rahul,

On 09/26/2015 07:04 AM, Rahul Bedarkar wrote:
> In notes section, statement
> 
> "(But note that the resources of all threads are freed when the
> process terminates.)"
> 
> is confusing and invalid. In Linux, we don't really need to wait
> until application termination for system resources to be freed unless
> there is bug in application logic.

While I'm not sure that that sentence is essential, it does serve
to remind the reader that all resources are freed on process
termination, regardless of whether pthread_detach() and pthread_join()
are used. 

It's not clear to me why you find it confusing or invalid.
Can you say more?

Thanks,

Michael


> Signed-off-by: Rahul Bedarkar <rahulbedarkar89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
>  man3/pthread_detach.3 | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/man3/pthread_detach.3 b/man3/pthread_detach.3
> index 106914b..2c53409 100644
> --- a/man3/pthread_detach.3
> +++ b/man3/pthread_detach.3
> @@ -101,8 +101,6 @@ or
>  .BR pthread_detach ()
>  should be called for each thread that an application creates,
>  so that system resources for the thread can be released.
> -(But note that the resources of all threads are freed when the
> -process terminates.)
>  .SH EXAMPLE
>  The following statement detaches the calling thread:
>  
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-10-08 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-26  6:04 [RFC PATCH 1/1] pthread_detach.3: remove invalid and confusing statement Rahul Bedarkar
     [not found] ` <1443247457-3507-1-git-send-email-rahulbedarkar89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-08 21:10   ` Michael Kerrisk (man-pages) [this message]
     [not found]     ` <5616DBB4.7060903-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-13  3:48       ` Rahul Bedarkar
     [not found]         ` <CA+NV+Vmh7SHoqyToYbznHeO6qgr=c0dfw=4hnT5d0=VSNP5eNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-29 16:25           ` Michael Kerrisk (man-pages)
     [not found]             ` <CAKgNAkhK=dS=dREBdoo3ROwwQ3GXRH5C+dhtAW6GgdyA4mfUNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-10 13:30               ` Rahul Bedarkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5616DBB4.7060903@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rahulbedarkar89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.