aboutsummaryrefslogtreecommitdiff
path: root/docs/libcurl
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2006-02-17 13:31:49 +0000
committerDaniel Stenberg <daniel@haxx.se>2006-02-17 13:31:49 +0000
commit98180b5cc7981fe7ec93abfeb90513d6165f561f (patch)
tree9b8427cb5b8d24eb1450e44a438c3397c41df785 /docs/libcurl
parent92009181af0c4c5608b7e7378e2ea21806ee5e33 (diff)
fixed formatting
Diffstat (limited to 'docs/libcurl')
-rw-r--r--docs/libcurl/curl_global_cleanup.324
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/libcurl/curl_global_cleanup.3 b/docs/libcurl/curl_global_cleanup.3
index 3c7724d34..4cb13a7da 100644
--- a/docs/libcurl/curl_global_cleanup.3
+++ b/docs/libcurl/curl_global_cleanup.3
@@ -2,7 +2,7 @@
.\" nroff -man [file]
.\" $Id$
.\"
-.TH curl_global_cleanup 3 "28 May 2001" "libcurl 7.8" "libcurl Manual"
+.TH curl_global_cleanup 3 "17 Feb 2006" "libcurl 7.8" "libcurl Manual"
.SH NAME
curl_global_cleanup - global libcurl cleanup
.SH SYNOPSIS
@@ -11,20 +11,20 @@ curl_global_cleanup - global libcurl cleanup
.BI "void curl_global_cleanup(void);"
.ad
.SH DESCRIPTION
-This function releases resources acquired by \fBcurl_global_init\fP.
+This function releases resources acquired by \fBcurl_global_init(3)\fP.
-You should call \fIcurl_global_cleanup()\fP once for each call you make
-to \fIcurl_global_init\fP, after you are done using libcurl.
+You should call \fIcurl_global_cleanup(3)\fP once for each call you make to
+\fIcurl_global_init(3)\fP, after you are done using libcurl.
-\fBThis function is not thread safe.\fP You must not call it when any
-other thread in the program (i.e. a thread sharing the same memory) is
-running. This doesn't just mean no other thread that is using
-libcurl. Because \fBcurl_global_cleanup()\fP calls functions of other
-libraries that are similarly thread unsafe, it could conflict with any
-other thread that uses these other libraries.
+\fBThis function is not thread safe.\fP You must not call it when any other
+thread in the program (i.e. a thread sharing the same memory) is running.
+This doesn't just mean no other thread that is using libcurl. Because
+\fBcurl_global_cleanup(3)\fP calls functions of other libraries that are
+similarly thread unsafe, it could conflict with any other thread that uses
+these other libraries.
-See the description in \fBlibcurl\fP(3) of global environment
-requirements for details of how to use this function.
+See the description in \fBlibcurl(3)\fP of global environment requirements for
+details of how to use this function.
.SH "SEE ALSO"
.BR curl_global_init "(3), "