Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] rpm: Flush old logs by change the DB_CONFIG
Date: Tue, 22 Nov 2011 12:09:32 -0600	[thread overview]
Message-ID: <4ECBE55C.5090703@windriver.com> (raw)
In-Reply-To: <ea4995cfbec9d75978131ba7566e30d3a20f99fa.1321516924.git.lei.mei@intel.com>

Acked-by:  Mark Hatle <mark.hatle@windriver.com>

(Note: this is the fix suggested by the rpm5 community.)

On 11/17/11 2:32 AM, Mei Lei wrote:
> Fixes [YOCTO #1174]
>
> Rpm logs will grow indefinitely, so change the config to flush those old logs.
>
> Signed-off-by: Mei Lei<lei.mei@intel.com>
> ---
>   .../recipes-devtools/rpm/rpm/rpm-log-auto-rm.patch |   12 ++++++++++++
>   meta/recipes-devtools/rpm/rpm_5.4.0.bb             |    5 +++--
>   2 files changed, 15 insertions(+), 2 deletions(-)
>   create mode 100644 meta/recipes-devtools/rpm/rpm/rpm-log-auto-rm.patch
>
> diff --git a/meta/recipes-devtools/rpm/rpm/rpm-log-auto-rm.patch b/meta/recipes-devtools/rpm/rpm/rpm-log-auto-rm.patch
> new file mode 100644
> index 0000000..aafa416
> --- /dev/null
> +++ b/meta/recipes-devtools/rpm/rpm/rpm-log-auto-rm.patch
> @@ -0,0 +1,12 @@
> +diff --git a/rpmdb/DB_CONFIG.in b/rpmdb/DB_CONFIG.in
> +index 8b94c94..e0b4689 100644
> +--- a/rpmdb/DB_CONFIG.in
> ++++ b/rpmdb/DB_CONFIG.in
> +@@ -4,6 +4,7 @@ set_data_dir		.
> + set_create_dir		.
> + set_lg_dir		./log
> + set_tmp_dir		./tmp
> ++set_flags 		db_log_autoremove on
> +
> + # -- thread_count must be>= 8
> + set_thread_count	64
> diff --git a/meta/recipes-devtools/rpm/rpm_5.4.0.bb b/meta/recipes-devtools/rpm/rpm_5.4.0.bb
> index f8fe836..d14bce4 100644
> --- a/meta/recipes-devtools/rpm/rpm_5.4.0.bb
> +++ b/meta/recipes-devtools/rpm/rpm_5.4.0.bb
> @@ -45,11 +45,12 @@ LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1"
>   DEPENDS = "bzip2 zlib db openssl elfutils expat libpcre attr acl popt ${extrarpmdeps}"
>   extrarpmdeps = "python perl"
>   extrarpmdeps_virtclass-native = "file-native"
> -PR = "r23"
> +PR = "r24"
>
>   # rpm2cpio is a shell script, which is part of the rpm src.rpm.  It is needed
>   # in order to extract the distribution SRPM into a format we can extract...
>   SRC_URI = "http://www.rpm5.org/files/rpm/rpm-5.4/rpm-5.4.0-0.20101229.src.rpm;extract=rpm-5.4.0.tar.gz \
> +	   file://rpm-log-auto-rm.patch \
>   	   file://perfile_rpmdeps.sh \
>   	   file://rpm-autogen.patch \
>   	   file://rpm-libsql-fix.patch \
> @@ -192,6 +193,7 @@ FILES_${PN} = "${bindir}/rpm \
>   		${libdir}/rpm/bin/rpmrepo \
>   		${libdir}/rpm/bin/rpmspecdump \
>   		${libdir}/rpm/bin/wget \
> +		/var/lib/rpm \
>   		"
>
>   #		${libdir}/rpm/magic
> @@ -208,7 +210,6 @@ FILES_${PN}-dbg += "${libdir}/rpm/.debug \
>   FILES_${PN}-common = "${bindir}/rpm2cpio \
>   		${bindir}/gendiff \
>   		/etc/rpm \
> -		/var/lib/rpm \
>   		/var/spool/repackage \
>   		"
>




  reply	other threads:[~2011-11-22 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  8:32 [PATCH 0/1]rpm: Fix rpm log grows indefinitely issue Mei Lei
2011-11-17  8:32 ` [PATCH 1/1] rpm: Flush old logs by change the DB_CONFIG Mei Lei
2011-11-22 18:09   ` Mark Hatle [this message]
2011-11-25  0:01   ` Richard Purdie

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=4ECBE55C.5090703@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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