Docs/defensive-coding-guide
2
0
Fork 0
Code Issues 3 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Update Tasks-Descriptors.xml - typos fixed

Browse source
This commit is contained in:
Mirek Jahoda 2017-10-23 15:36:22 +00:00
parent d0c00172ee
commit 0ddff13b56
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
en-US/Tasks-Descriptors.xml
View file

@ -24,7 +24,7 @@
itself, see <xref
linkend="sect-Defensive_Coding-Tasks-Descriptors-Limit"/>), and
the kernel resources are not freed. Therefore, it is important
to close all descriptors at the earlierst point in time
to close all descriptors at the earliest point in time
possible, but not earlier.
</para>
<section>
@ -54,7 +54,7 @@
descriptors, descriptors are reused very quickly. Unless
descriptor closing and other operations on the same file
descriptor are synchronized (typically, using a mutex), there
will be race coniditons and I/O operations will be applied to
will be race conditons and I/O operations will be applied to
the wrong file descriptor.
</para>
<para>
@ -176,7 +176,7 @@
Traditionally, this was implemented as a loop over file
descriptors ranging from <literal>3</literal> to
<literal>255</literal> and later <literal>1023</literal>.
But this is only an approximatio because it is possible to
But this is only an approximation because it is possible to
create file descriptors outside this range easily (see <xref
linkend="sect-Defensive_Coding-Tasks-Descriptors-Limit"/>).
Another approach reads <filename>/proc/self/fd</filename>