Tuning Changelogs

Some packages have a long list of changelog entries. This data is downloaded by default, but it is not always useful information to keep. In order to limit the amount of changelog metadata which is downloaded and to save disk space, you can put a limit on how many entries to keep on disk.

This configuration option is in the /etc/rhn/rhn.conf configuration file. The parameter defaults to 0, which means unlimited.

java.max_changelog_entries = 0

If you set this parameter, it will come into effect only for new packages when they are synchronized. You might like to delete the cached data to remove older data.

Deleting cached data can take a long time. Depending on the number of channels you have and the amount of data to be deleted, it can potentially take several hours. The task is run in the background by Taskomatic, so you can continue to use Uyuni while the operation completes, however you should expect some performance loss.

You can delete cached data from the command line, using the SQL interface:

spacewalk-sql -i
SQL> delete from rhnPackageRepodata;
SQL> insert into rhnRepoRegenQueue (id, CHANNEL_LABEL, REASON, FORCE)
(select sequence_nextval('rhn_repo_regen_queue_id_seq'),
        C.label,
        'package summary modification',
        'Y'
   from rhnChannel C);
SQL> \q