From: Dave Oxley <dave@daveoxley.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] distfiles on samba and 2.6.18
Date: Thu, 09 Nov 2006 15:04:04 +1100 [thread overview]
Message-ID: <4552A8B4.5000001@daveoxley.co.uk> (raw)
In-Reply-To: <20061106144204.dfb8cf40.hilse@web.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hans-Werner Hilse wrote:
> Hi,
>
> On Mon, 06 Nov 2006 00:09:23 +1100 Dave Oxley <dave@daveoxley.co.uk>
> wrote:
>
>> Since upgrading to the 2.6.18 kernel I get this on my client machine
>> when trying to emerge. I have distfiles mapped to a server samba share
>> and this works if I boot back up into 2.6.17. Does anyone have any
>> ideas how to stop this happening?
>> [...]
>> File "/usr/lib/portage/pym/portage_locks.py", line 159, in
>> unlockfile locking_method(myfd,fcntl.LOCK_UN)
>> IOError: [Errno 13] Permission denied
>> Error in sys.exitfunc:
>
> Look at /etc/make.conf.example:
>
> First try cleaning the locks using
> /usr/lib/portage/bin/clean_locks
> If that doesn't work, you have more options:
> - specify a PORTAGE_TMPFS (albeit I'm not sure if this applies for
> distfiles locks, too),
> - remove "distlocks" FEATURE.
>
> -hwh
Cleaning the locks had no effect. Neither did setting PORTAGE_TMPFS. I
had to remove distlocks which also disabled parallel-fetching. I don't
understand why this only happens with 2.6.18 and it seems like a bug,
but at least I can continue to use my samba share distfiles now.
Cheers,
Dave.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFUqi0x43ifHzpDVURAqGDAJ9HZKa1kXhpL/mYJplqNvwWKRxlFgCfYNQv
HAdXuzRyxbY1LIMlNNvx6V0=
=e91e
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2006-11-09 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 13:09 [gentoo-user] distfiles on samba and 2.6.18 Dave Oxley
2006-11-06 13:42 ` Hans-Werner Hilse
2006-11-09 4:04 ` Dave Oxley [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=4552A8B4.5000001@daveoxley.co.uk \
--to=dave@daveoxley.co.uk \
--cc=gentoo-user@lists.gentoo.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