public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sven Vermeulen (swift)" <swift@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/doc/en/security: shb-limits.xml
Date: Tue, 15 Nov 2011 18:53:00 +0000 (UTC)	[thread overview]
Message-ID: <20111115185300.280132004C@flycatcher.gentoo.org> (raw)

swift       11/11/15 18:53:00

  Modified:             shb-limits.xml
  Log:
  Fix bug #387105 - quotacheck should not be scheduled, it is a repair tool. Thanks to Oleg Gawriloff for reporting

Revision  Changes    Path
1.11                 xml/htdocs/doc/en/security/shb-limits.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/security/shb-limits.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/security/shb-limits.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/security/shb-limits.xml?r1=1.10&r2=1.11

Index: shb-limits.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-limits.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- shb-limits.xml	2 Mar 2011 08:52:47 -0000	1.10
+++ shb-limits.xml	15 Nov 2011 18:53:00 -0000	1.11
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-limits.xml,v 1.10 2011/03/02 08:52:47 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-limits.xml,v 1.11 2011/11/15 18:53:00 swift Exp $ -->
 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
 
 <!-- The content of this document is licensed under the CC-BY-SA license -->
@@ -7,8 +7,8 @@
 
 <sections>
 
-<version>2</version>
-<date>2011-03-02</date>
+<version>3</version>
+<date>2011-11-15</date>
 
 <section id="limits_conf">
 <title>/etc/security/limits.conf</title>
@@ -138,14 +138,13 @@
 </pre>
 
 <p>
-We will now configure the system to check the quotas once a week by adding the
-following line to <path>/etc/crontab</path>:
+The Linux kernel will track the quota usage as the system works. If for any
+reason the quota files become corrupt or you think the data is wrong, you will
+need to bring the system in single-user mode (or at least ensure that the file
+systems are not being actively written to) and then call <c>quotacheck
+-avugm</c>.
 </p>
 
-<pre caption="Adding quota check to crontab">
-0 3 * * 0 /usr/sbin/quotacheck -avug.
-</pre>
-
 <p>
 After rebooting the machine, it is time to setup the quotas for users and
 groups. <c>edquota -u kn</c> will start the editor defined in $EDITOR (default






             reply	other threads:[~2011-11-15 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15 18:53 Sven Vermeulen (swift) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-02  8:52 [gentoo-commits] gentoo commit in xml/htdocs/doc/en/security: shb-limits.xml Joshua Saddler (nightmorph)
2010-04-26 22:14 Joshua Saddler (nightmorph)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111115185300.280132004C@flycatcher.gentoo.org \
    --to=swift@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox