| 1 |
Daniel Campbell <zlg@g.o> writes: |
| 2 |
|
| 3 |
> On 11/19/2016 04:21 PM, Harry Putnam wrote: |
| 4 |
>> Mick <michaelkintzios@×××××.com> writes: |
| 5 |
>> |
| 6 |
>>> On Saturday 19 Nov 2016 08:54:53 Harry Putnam wrote: |
| 7 |
>>>> After looking thru the portage man pages, the make.conf.example in |
| 8 |
>>>> /usr/share/portage/config, and the `Portage log wiki' it still is not |
| 9 |
>>>> clear to me how long elogs are kept if you use the `save' flag in |
| 10 |
>>>> make.conf or not. |
| 11 |
>>>> |
| 12 |
>>>> I did see something about '7 days' but it was not clear if that is the |
| 13 |
>>>> default and `save' over-rides it or what. Or if there is another flag |
| 14 |
>>>> that controls there duration... |
| 15 |
>>>> |
| 16 |
>>>> Can anyone throw light on that? |
| 17 |
>>> |
| 18 |
>>> If you have logrotate then its configuration and associated cron jobs will take |
| 19 |
>>> care of that. |
| 20 |
>> |
| 21 |
>> What I want to know is if the elog program will do something on its |
| 22 |
>> own... I'm wanting to hang on to the logs a good while... I saw |
| 23 |
>> something in my readings about the elog system about 7 days... was not |
| 24 |
>> clear if that is a defalult or what. |
| 25 |
>> |
| 26 |
>> So my fear was losing them even if I am logrotate at them in some |
| 27 |
>> capacity. So I'm asking about inside the elog program... what happens |
| 28 |
>> to the logs and when. |
| 29 |
>> |
| 30 |
>> |
| 31 |
> According to make.conf.example, PORTAGE_ELOG_SYSTEM="save" creates one |
| 32 |
> log per package under $PORT_LOGDIR/elog (/var/log/portage/elog if unset). |
| 33 |
> |
| 34 |
> What this means is Portage will continue to use whatever path you have |
| 35 |
> specified, and it's up to your syslogd or logrotate to determine whether |
| 36 |
> those particular logs get deleted. |
| 37 |
> |
| 38 |
> I suggest looking through /etc/logrotate{.conf,.d/} and grokking things |
| 39 |
> to determine how long your elogs will last. On my system, I noticed I |
| 40 |
> have /etc/logrotate.d/elog-save-summary, so if you find a file like |
| 41 |
> that, it's a good place to start. Without logrotate handling it, I see |
| 42 |
> no reason to believe Portage will nix elog output after 7 days. |
| 43 |
> |
| 44 |
|
| 45 |
> In case I've missed something, could you link to the page that mentions |
| 46 |
> 7 days? I searched through manpages and the wiki but haven't found any |
| 47 |
> other "save" option or anything to do with elog and 7 days. |
| 48 |
|
| 49 |
https://wiki.gentoo.org/wiki/Portage_log |
| 50 |
|
| 51 |
[About mid page ... But this may not be considered `elogs'... ] |
| 52 |
|
| 53 |
Next, a number of FEATURES settings influence how Portage handles build logs. |
| 54 |
|
| 55 |
With binpkg-logs set, even binary package deployments will have their |
| 56 |
logs saved |
| 57 |
|
| 58 |
When clean-logs is set, regular log file clean operations are |
| 59 |
executed. The command that is executed is defined by PORT_LOGDIR_CLEAN |
| 60 |
and defaults to a retention of the files of 7 days. |
| 61 |
|
| 62 |
With split-log set, build logs are stored in category-named |
| 63 |
subdirectories of ${PORT_LOGDIR}/build |
| 64 |
|
| 65 |
When clean-logs is set, Portage will execute the command defined by |
| 66 |
PORT_LOGDIR_CLEAN after every build or unmerge operation. By |
| 67 |
default, the following command is used: |
Archives