Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Never ending stream of bitbake exceptions when the builder runs out of disk space
Date: Tue, 27 Jun 2017 10:37:53 +0100	[thread overview]
Message-ID: <1498556273.3124.6.camel@linuxfoundation.org> (raw)
In-Reply-To: <1498555300.7464.35.camel@intel.com>

On Tue, 2017-06-27 at 11:21 +0200, Patrick Ohly wrote:
> On Tue, 2017-06-27 at 09:25 +0100, Richard Purdie wrote:
> > 
> > So if its not default, we should make it default and I'd encourage
> > people to use it.
> It's not the default at the moment because it's only in
> local.conf.sample, which people might not use.
> 
> So should a default for BB_DISKMON_DIRS be set in bitbake.conf?

No, I don't think this belongs in bitbake.conf.

If you use a nodistro setup you do get a reasonable default value for
this, you're right and it is in the default local.conf.sample. Its up
to distros and users to select the pieces they need/want beyond that.
Whilst Martin is close to nodistro it sounds like this config was
missing and I'd suggest using it.

Cheers,

Richard



  reply	other threads:[~2017-06-27  9:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15  6:48 Never ending stream of bitbake exceptions when the builder runs out of disk space Martin Jansa
2017-06-27  8:08 ` Patrick Ohly
2017-06-27  8:12   ` Martin Jansa
2017-06-27  8:25     ` Richard Purdie
2017-06-27  9:21       ` Patrick Ohly
2017-06-27  9:37         ` Richard Purdie [this message]
2017-06-27 13:00           ` Martin Jansa
2017-06-27  9:41   ` 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=1498556273.3124.6.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patrick.ohly@intel.com \
    /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