Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Feb 2013 16:42:43 -0500 (EST)
From:      Benjamin Kaduk <kaduk@MIT.EDU>
To:        Dru Lavigne <dru@freebsd.org>
Cc:        svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org
Subject:   Re: svn commit: r41024 - head/en_US.ISO8859-1/books/handbook/users
Message-ID:  <alpine.GSO.1.10.1302211348170.9389@multics.mit.edu>
In-Reply-To: <201302211406.r1LE66bl041470@svn.freebsd.org>
References:  <201302211406.r1LE66bl041470@svn.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Feb 2013, Dru Lavigne wrote:

> Modified: head/en_US.ISO8859-1/books/handbook/users/chapter.xml
> ==============================================================================
> --- head/en_US.ISO8859-1/books/handbook/users/chapter.xml	Wed Feb 20 19:00:52 2013	(r41023)
> +++ head/en_US.ISO8859-1/books/handbook/users/chapter.xml	Thu Feb 21 14:06:06 2013	(r41024)
> @@ -161,10 +155,10 @@
> 	<term>Password change time</term>
>
> 	<listitem>
> -	  <para>By default FreeBSD does not force users to change
> -	    their passwords periodically.  You can enforce this on a
> -	    per-user basis, forcing some or all of your users to
> -	    change their passwords after a certain amount of time has
> +	  <para>By default &os; does not force users to change their
> +	    passwords periodically.  This can be enforced on a

"This" is rather vague, and if taken literally probably refers to *not* 
forcing users to change their password periodically.  It should probably 
be replaced with "Password expiration" in this instance.

> +	    per-user basis, forcing some or all users to change their
> +	    passwords after a certain amount of time has
> 	    elapsed.</para>
> 	</listitem>
>       </varlistentry>
> @@ -700,11 +683,9 @@ passwd: done</screen>
>       <secondary>quotas</secondary>
>     </indexterm>
>     <indexterm><primary>disk quotas</primary></indexterm>
> -    <para>Disk quotas limit disk usage to users, and
> -      they
> -      provide a way to quickly check that usage without
> -      calculating it every time.  Quotas are discussed in <xref
> -	linkend="quotas"/>.</para>
> +    <para>Disk quotas limit disk usage to users and provide a way to
> +      quickly check that usage without calculating it every time.

This sentence is still not quite there.
Maybe "Disk quotas limit the disk usage available to users" or "limit the 
disk usage of users"?

> +      Quotas are discussed in <link linkend="quotas"></link>.</para>
>
>     <para>The other resource limits include ways to limit the amount
>       of CPU, memory, and other resources a user may consume.  These
> @@ -714,47 +695,45 @@ passwd: done</screen>
>       login capability is a
>       <literal><replaceable>name</replaceable>=<replaceable>value</replaceable></literal>
>       pair, where <replaceable>name</replaceable> is a well-known
>       identifier and <replaceable>value</replaceable> is an arbitrary
> -      string processed accordingly depending on the name.  Setting up
> -      login classes and capabilities is rather straight-forward and is
> -      also described in &man.login.conf.5;.</para>
> +      string which is processed accordingly depending on the
> +      <replaceable>name</replaceable>.  Setting up login classes and
> +      capabilities is rather straight-forward and is also described in
> +      &man.login.conf.5;.</para>

I believe straightforward does not normally take a hyphen.

> @@ -850,12 +822,11 @@ passwd: done</screen>
> 	    <primary>limiting users</primary>
> 	    <secondary>memorylocked</secondary>
> 	  </indexterm>
> -	  <para>This is the maximum amount a memory a process may have
> -	    requested to be locked into main memory (e.g., see
> -	    &man.mlock.2;).  Some system-critical programs, such as
> -	    &man.amd.8;, lock into main memory such that in the event
> -	    of being swapped out, they do not contribute to
> -	    a system's thrashing in time of trouble.</para>
> +	  <para>The maximum amount of memory a process may request
> +	    to be locked into main memory using &man.mlock.2;.  Some
> +	    system-critical programs, such as &man.amd.8;, lock into
> +	    main memory so that in the event of being swapped out,
> +	    they do not contribute to disk thrashing.</para>

"in the event of being swapped out" is confusing at best, here.
I would probably just put "so that if the system begins to swap, they do 
not".

> 	</listitem>
>       </varlistentry>
>
> @@ -882,10 +852,10 @@ passwd: done</screen>
> 	  <indexterm><primary>limiting users</primary>
> 	    <secondary>openfiles</secondary>
> 	  </indexterm>
> -	  <para>This is the maximum amount of files a process may have
> -	    open.  In FreeBSD, files are also used to represent
> -	    sockets and IPC channels; thus, be careful not to set this
> -	    too low.  The system-wide limit for this is defined by the
> +	  <para>The maximum amount of files a process may have open.

Files are discrete objects and should probably be quantified as a number, 
not an amount.

-Ben

> +	    In &os;, files are used to represent sockets and IPC
> +	    channels, so be careful not to set this too low.  The
> +	    system-wide limit for this is defined by the
> 	    <varname>kern.maxfiles</varname> &man.sysctl.8;.</para>
> 	</listitem>
>       </varlistentry>
>
> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1302211348170.9389>