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

Update Tasks-File_System.xml - Title Case fixed

Browse source
This commit is contained in:
Mirek Jahoda 2017-10-20 11:02:31 +00:00
parent c755d1610c
commit 9081a72a29
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
en-US/Tasks-File_System.xml
View file

@ -2,7 +2,7 @@
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]> ]>
<chapter id="chap-Defensive_Coding-Tasks-File_System"> <chapter id="chap-Defensive_Coding-Tasks-File_System">
<title>File system manipulation</title> <title>File System Manipulation</title>
<para> <para>
In this chapter, we discuss general file system manipulation, with In this chapter, we discuss general file system manipulation, with
a focus on access files and directories to which an other, a focus on access files and directories to which an other,
@ -13,7 +13,7 @@
linkend="chap-Defensive_Coding-Tasks-Temporary_Files"/>. linkend="chap-Defensive_Coding-Tasks-Temporary_Files"/>.
</para> </para>
<section id="sect-Defensive_Coding-Tasks-File_System-Unowned"> <section id="sect-Defensive_Coding-Tasks-File_System-Unowned">
<title>Working with files and directories owned by other users</title> <title>Working with Files and Directories Owned by Other Users</title>
<para> <para>
Sometimes, it is necessary to operate on files and directories Sometimes, it is necessary to operate on files and directories
owned by other (potentially untrusted) users. For example, a owned by other (potentially untrusted) users. For example, a
@ -145,7 +145,7 @@
</para> </para>
</section> </section>
<section id="sect-Defensive_Coding-Tasks-File_System-Foreign"> <section id="sect-Defensive_Coding-Tasks-File_System-Foreign">
<title>Accessing the file system as a different user</title> <title>Accessing the File System as a Different User</title>
<para> <para>
This section deals with access to the file system as a specific This section deals with access to the file system as a specific
user. This is different from accessing files and directories owned by a user. This is different from accessing files and directories owned by a
@ -178,7 +178,7 @@
</para> </para>
</section> </section>
<section id="sect-Defensive_Coding-Tasks-File_System-Limits"> <section id="sect-Defensive_Coding-Tasks-File_System-Limits">
<title>File system limits</title> <title>File System Limits</title>
<para> <para>
For historical reasons, there are preprocessor constants such as For historical reasons, there are preprocessor constants such as
<literal>PATH_MAX</literal>, <literal>NAME_MAX</literal>. <literal>PATH_MAX</literal>, <literal>NAME_MAX</literal>.
@ -320,7 +320,7 @@
</itemizedlist> </itemizedlist>
</section> </section>
<section id="sect-Defensive_Coding-Tasks-File_System-Free_Space"> <section id="sect-Defensive_Coding-Tasks-File_System-Free_Space">
<title>Checking free space</title> <title>Checking Free Space</title>
<para> <para>
The <function>statvfs</function> and The <function>statvfs</function> and
<function>fstatvfs</function> functions allow programs to <function>fstatvfs</function> functions allow programs to