| 1 |
Zac Medico schrieb: |
| 2 |
> Stefan G. Weichinger wrote: |
| 3 |
>> Greetings, gentoo-users, |
| 4 |
> |
| 5 |
>> I see a problem with emerge on my notebook. |
| 6 |
> |
| 7 |
>> Whenever I try to emerge something, it starts off like: |
| 8 |
> |
| 9 |
>> # emerge -1 libsexy |
| 10 |
>> Calculating dependencies... done! |
| 11 |
>>>>> Verifying ebuild Manifests... |
| 12 |
>>>>> Emerging (1 of 1) x11-libs/libsexy-0.1.11 to / |
| 13 |
>> and then just hangs there, doing nothing. |
| 14 |
> |
| 15 |
> That's right where it attempts to obtain a lock on the required |
| 16 |
> files in ${DISTDIR}. If that's on nfs and nfs isn't behaving |
| 17 |
> properly then it can cause problems like that. Check dmesg. |
| 18 |
|
| 19 |
Correct, my ${DISTDIR} is normally mounted via nfs. |
| 20 |
When I umount it, I can emerge ... |
| 21 |
|
| 22 |
When mounted, dmesg gives me |
| 23 |
|
| 24 |
lockd: cannot monitor ${IP_OF_NFS_SERVER} |
| 25 |
lockd: failed to monitor ${IP_OF_NFS_SERVER} |
| 26 |
|
| 27 |
What can I do to fix this? Restarting the nfs-service on the server did |
| 28 |
not help yet. |
| 29 |
|
| 30 |
Thanks a lot, Stefan |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-user@g.o mailing list |
Archives