Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] bitbake: Add pyinotify to lib/
Date: Tue, 20 Jan 2015 06:53:15 +0800	[thread overview]
Message-ID: <54BD8ADB.1090600@windriver.com> (raw)
In-Reply-To: <1421663325.1798.31.camel@linuxfoundation.org>



On 01/19/2015 06:28 PM, Richard Purdie wrote:
> On Mon, 2015-01-19 at 16:10 +0800, Robert Yang wrote:
>> The inotify watcher numbers need less than "sysctl -n fs.inotify.max_user_watches",
>> otherwise we may get the errors like:
>> WatchManagerError: add_watch: cannot watch /path/to/build/conf/bblayers.conf
>> WD=-1, Errno=No space left on device (ENOSPC),
>>
>> It's easy to meet this error if we run many builds at the same time,
>> On Ubuntu Ubuntu 12.04.3 x86_64, the default value is "8192".
>>
>> Can we add some counters in cooker.py (or other files) to check the
>> value and print ERRORS/WARNINGS, please ? Ther current "ENOSPC" errors
>> is not easy to debug.
>>
>> I'd like to work on it if that make sense.
>
> Surely we should just trap the ENOSPC error and translate it into a
> human readable error message? I don't like the idea of adding counters
> into the system.
>
> To improve the situation from a variety of perspectives, I'm thinking we
> should perhaps just place watches on the directories containing the
> files rather than the files themselves since this would drastically
> reduce the number of watches we need. The downside is we may have to be
> more careful about how we invalidate the caches.

Thanks, watch dirs seems reasonable, I will do more investigations on it.

// Robert

>
> Cheers,
>
> Richard
>
>
>


  reply	other threads:[~2015-01-19 22:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 14:11 [PATCH] bitbake: Add pyinotify to lib/ Richard Purdie
2015-01-19  8:10 ` Robert Yang
2015-01-19 10:28   ` Richard Purdie
2015-01-19 22:53     ` Robert Yang [this message]
2015-01-20  2:25     ` Robert Yang
2015-01-20  8:55       ` Richard Purdie
2015-01-20  9:06         ` Robert Yang
2015-01-20  9:33         ` Robert Yang
2015-01-22  9:10       ` Robert Yang
2015-01-22 12:50         ` Burton, Ross
2015-01-23  0:54           ` Robert Yang
2015-01-23  1:11             ` Robert Yang

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=54BD8ADB.1090600@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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