This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH][BZ #14872] Mention if terminating null is included inNAME_MAX/PATH_MAX


Hi,

Attached patch explicitly mentions if the terminating null is included
in the sizes specified in NAME_MAX and PATH_MAX.  OK to commit?

Siddhesh

2012-12-10  Siddhesh Poyarekar  <siddhesh@redhat.com>

	[BZ #14872]
	* manual/conf.texi (Limits on File System Capacity): Mention if
	terminating null is included in the max size.

diff --git a/manual/conf.texi b/manual/conf.texi
index 61dc260..62b7d15 100644
--- a/manual/conf.texi
+++ b/manual/conf.texi
@@ -1147,14 +1147,16 @@ typed ahead as input.  @xref{I/O Queues}.
 @comment limits.h
 @comment POSIX.1
 @deftypevr Macro int NAME_MAX
-The uniform system limit (if any) for the length of a file name component.
+The uniform system limit (if any) for the length of a file name component, not
+including the terminating null.
 @end deftypevr
 
 @comment limits.h
 @comment POSIX.1
 @deftypevr Macro int PATH_MAX
 The uniform system limit (if any) for the length of an entire file name (that
-is, the argument given to system calls such as @code{open}).
+is, the argument given to system calls such as @code{open}), including the
+terminating null.
 @end deftypevr
 
 @cindex limits, pipe buffer size


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]