From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@openembedded.org
Subject: Re: Cached MD5 sums
Date: Wed, 12 Sep 2007 14:53:48 +0200 [thread overview]
Message-ID: <46E7E15C.3FA5AC70@vollmann.ch> (raw)
In-Reply-To: HOECLKEKOHLAMMGDLLBHOENOMDAA.skoroneos@digital-opsis.com
Stelios Koroneos wrote:
>
> We had a similar problem when the sources resided in an nfs mount.
> Is this the case with your sourse/md5 files ?
Interesing hint.
I don't have an NFS mount now. But I'm inside of a chroot environment
and previously had an NFS mount from outside the chroot into
inside (on the same machine and even the same physical filesystem).
But I got locking problems and decided to move the DL_DIR into
the chroot. But probably there's still some wrong info in
the cache, but it still complains about not being able to lock,
though a can lock on exactly the same file inside the same chroot
using my own test program. I had to hack bitbake (remove the
locking) to get around this).
> If yes you need to have statd running on *both* client and server machines
> In debian/ubuntu just install the nfs-common package and it solves the issue
For real NFS mount from one machine to the other I never had
problems, and probably I should do just that and start completely
fresh...
Thanks again,
Detlef
--
Detlef Vollmann vollmann engineering gmbh
Linux and C++ for Embedded Systems http://www.vollmann.ch/
prev parent reply other threads:[~2007-09-12 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 22:30 Cached MD5 sums Detlef Vollmann
2007-09-12 5:55 ` Stelios Koroneos
2007-09-12 12:53 ` Detlef Vollmann [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=46E7E15C.3FA5AC70@vollmann.ch \
--to=dv@vollmann.ch \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.