1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hans-Werner Hilse wrote: |
5 |
> Hi, |
6 |
> |
7 |
> On Mon, 06 Nov 2006 00:09:23 +1100 Dave Oxley <dave@××××××××××××.uk> |
8 |
> wrote: |
9 |
> |
10 |
>> Since upgrading to the 2.6.18 kernel I get this on my client machine |
11 |
>> when trying to emerge. I have distfiles mapped to a server samba share |
12 |
>> and this works if I boot back up into 2.6.17. Does anyone have any |
13 |
>> ideas how to stop this happening? |
14 |
>> [...] |
15 |
>> File "/usr/lib/portage/pym/portage_locks.py", line 159, in |
16 |
>> unlockfile locking_method(myfd,fcntl.LOCK_UN) |
17 |
>> IOError: [Errno 13] Permission denied |
18 |
>> Error in sys.exitfunc: |
19 |
> |
20 |
> Look at /etc/make.conf.example: |
21 |
> |
22 |
> First try cleaning the locks using |
23 |
> /usr/lib/portage/bin/clean_locks |
24 |
> If that doesn't work, you have more options: |
25 |
> - specify a PORTAGE_TMPFS (albeit I'm not sure if this applies for |
26 |
> distfiles locks, too), |
27 |
> - remove "distlocks" FEATURE. |
28 |
> |
29 |
> -hwh |
30 |
|
31 |
Cleaning the locks had no effect. Neither did setting PORTAGE_TMPFS. I |
32 |
had to remove distlocks which also disabled parallel-fetching. I don't |
33 |
understand why this only happens with 2.6.18 and it seems like a bug, |
34 |
but at least I can continue to use my samba share distfiles now. |
35 |
|
36 |
Cheers, |
37 |
Dave. |
38 |
-----BEGIN PGP SIGNATURE----- |
39 |
Version: GnuPG v1.4.5 (GNU/Linux) |
40 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
41 |
|
42 |
iD8DBQFFUqi0x43ifHzpDVURAqGDAJ9HZKa1kXhpL/mYJplqNvwWKRxlFgCfYNQv |
43 |
HAdXuzRyxbY1LIMlNNvx6V0= |
44 |
=e91e |
45 |
-----END PGP SIGNATURE----- |
46 |
-- |
47 |
gentoo-user@g.o mailing list |