summaryrefslogtreecommitdiffstats
path: root/lib/libc
diff options
context:
space:
mode:
authorbrucec <brucec@FreeBSD.org>2010-09-11 10:49:56 +0000
committerbrucec <brucec@FreeBSD.org>2010-09-11 10:49:56 +0000
commit7adc5f91cff836324150e37db070cf854b475e73 (patch)
tree9b0dbb739b35e3d9e69dd5c1d72fd4a2c349c473 /lib/libc
parent6b5a9d0d4bcef5193a4b10feee02073eeb9ec0ff (diff)
downloadFreeBSD-src-7adc5f91cff836324150e37db070cf854b475e73.zip
FreeBSD-src-7adc5f91cff836324150e37db070cf854b475e73.tar.gz
Revert changes of 'assure' to 'ensure' made in r211936.
Approved by: rrs (mentor)
Diffstat (limited to 'lib/libc')
-rw-r--r--lib/libc/net/sctp_send.34
-rw-r--r--lib/libc/net/sctp_sendmsg.34
-rw-r--r--lib/libc/stdio/printf.32
-rw-r--r--lib/libc/stdlib/malloc.34
4 files changed, 7 insertions, 7 deletions
diff --git a/lib/libc/net/sctp_send.3 b/lib/libc/net/sctp_send.3
index 8d860df..9acb616 100644
--- a/lib/libc/net/sctp_send.3
+++ b/lib/libc/net/sctp_send.3
@@ -191,7 +191,7 @@ If that many milliseconds elapse
and the peer has not acknowledged the data, the data will be
skipped and no longer transmitted.
Note that this policy does
-not even ensure that the data will ever be sent.
+not even assure that the data will ever be sent.
In times of a congestion
with large amounts of data being queued, the
.Fa sinfo->sinfo_timetolive
@@ -218,7 +218,7 @@ policy transforms the
.Fa sinfo->sinfo_timetolive
into a number of retransmissions to allow.
This policy
-always ensures that at a minimum one send attempt is
+always assures that at a minimum one send attempt is
made of the data.
After which no more than
.Fa sinfo->sinfo_timetolive
diff --git a/lib/libc/net/sctp_sendmsg.3 b/lib/libc/net/sctp_sendmsg.3
index 1015558..ddd88b4 100644
--- a/lib/libc/net/sctp_sendmsg.3
+++ b/lib/libc/net/sctp_sendmsg.3
@@ -203,7 +203,7 @@ If that many milliseconds elapse
and the peer has not acknowledged the data, the data will be
skipped and no longer transmitted.
Note that this policy does
-not even ensure that the data will ever be sent.
+not even assure that the data will ever be sent.
In times of a congestion
with large amounts of data being queued, the
.Fa timetolive
@@ -230,7 +230,7 @@ policy transforms the
.Fa timetolive
into a number of retransmissions to allow.
This policy
-always ensures that at a minimum one send attempt is
+always assures that at a minimum one send attempt is
made of the data.
After which no more than
.Fa timetolive
diff --git a/lib/libc/stdio/printf.3 b/lib/libc/stdio/printf.3
index a0d2613..90a8ed8 100644
--- a/lib/libc/stdio/printf.3
+++ b/lib/libc/stdio/printf.3
@@ -849,7 +849,7 @@ and
.Fn vsprintf
assume an infinitely long string,
callers must be careful not to overflow the actual space;
-this is often hard to ensure.
+this is often hard to assure.
For safety, programmers should use the
.Fn snprintf
interface instead.
diff --git a/lib/libc/stdlib/malloc.3 b/lib/libc/stdlib/malloc.3
index 90781a1..2f21b6a 100644
--- a/lib/libc/stdlib/malloc.3
+++ b/lib/libc/stdlib/malloc.3
@@ -266,7 +266,7 @@ options are enabled, the allocator prefers anonymous mappings over the DSS,
but allocation only fails if memory cannot be acquired via either method.
If neither option is enabled, then the
.Dq M
-option is implicitly enabled in order to ensure that there is a method for
+option is implicitly enabled in order to assure that there is a method for
acquiring memory.
.It N
Double/halve the number of arenas.
@@ -437,7 +437,7 @@ rounded up to the nearest multiple of the chunk size.
.Pp
Allocations are packed tightly together, which can be an issue for
multi-threaded applications.
-If you need to ensure that allocations do not suffer from cacheline sharing,
+If you need to assure that allocations do not suffer from cacheline sharing,
round your allocation requests up to the nearest multiple of the cacheline
size.
.Sh DEBUGGING MALLOC PROBLEMS
OpenPOWER on IntegriCloud