From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Allow rotate log across filesystems
Date: Mon, 12 Mar 2012 14:11:50 -0700 [thread overview]
Message-ID: <4F5E6696.7050502@linux.intel.com> (raw)
In-Reply-To: <cover.1330956344.git.liezhi.yang@windriver.com>
On 03/05/2012 06:17 AM, Robert Yang wrote:
> This patch is based on oe-core, and the pull request is on poky-contrib
>
> The testing summary:
> 1) Add the olddir to logrotate.conf, and the olddir should have a
> different mount point of the current log directory.
>
> 2) Run "logrotate -f /path/to/logrotate.conf" to force rotate,
> the old log should be rotated to the olddir which is on another
> mount point.
>
> //Robert
>
> The following changes since commit a439d32dd843d10a9f65cc858b02422fac7deb50:
>
> soc-family.inc: to be included in machine.conf to add SOC_FAMILY to MACHINEOVERRIDE (2012-03-04 05:41:11 -0800)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib robert/logrotate
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/logrotate
>
> Robert Yang (1):
> logrotate 3.7.9: Allow rotate log across filesystems
>
> .../allow-across-different-filesystems.patch | 154 ++++++++++++++++++++
> meta/recipes-extended/logrotate/logrotate_3.7.9.bb | 5 +-
> 2 files changed, 157 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-extended/logrotate/logrotate-3.7.9/allow-across-different-filesystems.patch
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-03-12 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 14:17 [PATCH 0/1] Allow rotate log across filesystems Robert Yang
2012-03-05 14:17 ` [PATCH 1/1] logrotate 3.7.9: " Robert Yang
2012-03-12 21:11 ` Saul Wold [this message]
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=4F5E6696.7050502@linux.intel.com \
--to=sgw@linux.intel.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