From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C3CE01381F3 for ; Wed, 5 Dec 2012 04:05:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0E493E06CC; Wed, 5 Dec 2012 04:05:35 +0000 (UTC) Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 98C62E0686 for ; Wed, 5 Dec 2012 04:04:31 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id c50so2820499eek.40 for ; Tue, 04 Dec 2012 20:04:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Um3oeFB8+tdqsmyZnM8t7xJwQPeR9GU4FarlgFiU25M=; b=IcXGPGSkkxjdllqV5csu9RZL5x0Dd5eXOHm9Bd6mpgxsJEQa9SCmHXuIhWS4fpLYyV w+cWfvd9gjEWJN00sWc9JkIaSYvahx2GW0vDwYPcnzxo3UHN6eufIez8/blzvwIuF1PR jRWTjx0/gIPuAPvf9cecd3yMCMnxoyQIofieF7B9EBT9F/eraezkVUKz0R2RhU2wA4ju QYkaVxAaGkqjEQ7TMVTteC876dGMNdg+Z8DCJ8o/mSW/YG+U78s9jgiM7puelwzpoI1o sudCelQfacQiczmtwlXIpSI+tDxepeKT2qdNP5WFLXGhJHlm+BhSbHd8qE1gZG/U+JK5 FeFQ== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.14.198.67 with SMTP id u43mr56470082een.7.1354680270274; Tue, 04 Dec 2012 20:04:30 -0800 (PST) Received: by 10.223.60.69 with HTTP; Tue, 4 Dec 2012 20:04:30 -0800 (PST) In-Reply-To: <5c00f8dd-b7d0-40c7-90cd-cbff12abfd85@email.android.com> References: <5c00f8dd-b7d0-40c7-90cd-cbff12abfd85@email.android.com> Date: Tue, 4 Dec 2012 20:04:30 -0800 Message-ID: Subject: Re: [gentoo-user] System maintenance procedure? From: Grant To: Gentoo mailing list Content-Type: multipart/alternative; boundary=047d7b343b244b41e704d01314b4 X-Archives-Salt: 6a8af00c-7072-4ed2-8f77-1f3314c1f0eb X-Archives-Hash: f24e08621f382e4e3f1adfa7dcfea9da --047d7b343b244b41e704d01314b4 Content-Type: text/plain; charset=ISO-8859-1 >> My unattended daily system maintenance procedure is like this: >> >> layman -S >> emerge --sync >> emerge -pvDuN world >> emerge -pv --depclean >> eclean -p distfiles >> eclean -p packages >> >> And then attended like this: >> >> emerge -DuN world >> revdep-rebuild >> etc-update >> elogv >> emerge --depclean >> eclean distfiles >> eclean packages >> >> Am I missing any good stuff? >> >> - Grant > > > The first depclean is redundant, you haven't updated anything so it won't show anything useful. I only run depclean and revdep-rebuild weekly,I don't see a need to routinely do it more often, especially on slower systems. I do run eix-update and eix-update-remote after my daily sync.I run eix-test-obsolete from the weekly cron script. I should have said that I'm emailed the results of the first set of commands so the first depclean is there to let me know what would be removed after yesterday's update. eix-test-obsolete sounds nice. New addition! > Frequent cleaning of packages is not a good idea IMO, I like to keep the old veraions around for at least a few days, in case something unpleasant shows up and I want to roll back. I think you're right about that. Can I configure eclean to wait a certain number of days since a package was removed before cleaning it? Even if I only run it once per week, it could remove a package that was updated yesterday that I find out I need tomorrow. - Grant --047d7b343b244b41e704d01314b4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable >> My unattended daily system maintenance procedure is like this:
= >>
>> layman -S
>> emerge --sync
>> emerge= -pvDuN world
>> emerge -pv --depclean
>> eclean -p distf= iles
>> eclean -p packages
>>
>> And then attended like = this:
>>
>> emerge -DuN world
>> revdep-rebuild<= br>>> etc-update
>> elogv
>> emerge --depclean
>> eclean distfiles
>> eclean packages
>>
>&g= t; Am I missing any good stuff?
>>
>> - Grant
>
= >
> The first depclean is redundant, you haven't updated anyth= ing so it won't show anything useful. I only run depclean and revdep-re= build weekly,I don't see a need to routinely do it more often, especial= ly on slower systems. I do run eix-update and eix-update-remote after my da= ily sync.I run eix-test-obsolete from the weekly cron script.

I should have said that I'm emailed the results of the first set of= commands so the first depclean is there to let me know what would be remov= ed after yesterday's update.

eix-test-obsolete sound= s nice. =A0New addition!

> Frequent cleaning of packages is not a good idea IMO, I like to ke= ep the old veraions around for at least a few days, in case something unple= asant shows up and I want to roll back.

I think you're right abo= ut that. =A0Can I configure eclean to wait a certain number of days since a= package was removed before cleaning it? =A0Even if I only run it once per = week, it could remove a package that was updated yesterday that I find out = I need tomorrow.

- Grant
--047d7b343b244b41e704d01314b4--