| 1 |
>> My unattended daily system maintenance procedure is like this: |
| 2 |
>> |
| 3 |
>> layman -S |
| 4 |
>> emerge --sync |
| 5 |
>> emerge -pvDuN world |
| 6 |
>> emerge -pv --depclean |
| 7 |
>> eclean -p distfiles |
| 8 |
>> eclean -p packages |
| 9 |
>> |
| 10 |
>> And then attended like this: |
| 11 |
>> |
| 12 |
>> emerge -DuN world |
| 13 |
>> revdep-rebuild |
| 14 |
>> etc-update |
| 15 |
>> elogv |
| 16 |
>> emerge --depclean |
| 17 |
>> eclean distfiles |
| 18 |
>> eclean packages |
| 19 |
>> |
| 20 |
>> Am I missing any good stuff? |
| 21 |
>> |
| 22 |
>> - Grant |
| 23 |
> |
| 24 |
> |
| 25 |
> The first depclean is redundant, you haven't updated anything so it won't |
| 26 |
show anything useful. I only run depclean and revdep-rebuild weekly,I don't |
| 27 |
see a need to routinely do it more often, especially on slower systems. I |
| 28 |
do run eix-update and eix-update-remote after my daily sync.I run |
| 29 |
eix-test-obsolete from the weekly cron script. |
| 30 |
|
| 31 |
I should have said that I'm emailed the results of the first set of |
| 32 |
commands so the first depclean is there to let me know what would be |
| 33 |
removed after yesterday's update. |
| 34 |
|
| 35 |
eix-test-obsolete sounds nice. New addition! |
| 36 |
|
| 37 |
> Frequent cleaning of packages is not a good idea IMO, I like to keep the |
| 38 |
old veraions around for at least a few days, in case something unpleasant |
| 39 |
shows up and I want to roll back. |
| 40 |
|
| 41 |
I think you're right about that. Can I configure eclean to wait a certain |
| 42 |
number of days since a package was removed before cleaning it? Even if I |
| 43 |
only run it once per week, it could remove a package that was updated |
| 44 |
yesterday that I find out I need tomorrow. |
| 45 |
|
| 46 |
- Grant |
Archives