| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Stefan G. Weichinger wrote: |
| 5 |
>>>>>> Emerging (1 of 1) x11-libs/libsexy-0.1.11 to / |
| 6 |
>>> and then just hangs there, doing nothing. |
| 7 |
>> That's right where it attempts to obtain a lock on the required |
| 8 |
>> files in ${DISTDIR}. If that's on nfs and nfs isn't behaving |
| 9 |
>> properly then it can cause problems like that. Check dmesg. |
| 10 |
> |
| 11 |
> Correct, my ${DISTDIR} is normally mounted via nfs. |
| 12 |
> When I umount it, I can emerge ... |
| 13 |
> |
| 14 |
> When mounted, dmesg gives me |
| 15 |
> |
| 16 |
> lockd: cannot monitor ${IP_OF_NFS_SERVER} |
| 17 |
> lockd: failed to monitor ${IP_OF_NFS_SERVER} |
| 18 |
> |
| 19 |
> What can I do to fix this? Restarting the nfs-service on the server did |
| 20 |
> not help yet. |
| 21 |
|
| 22 |
There are also nfs services that you need to run on the client side. |
| 23 |
Maybe you need to do something like this: |
| 24 |
|
| 25 |
emerge --noreplace nfs-utils |
| 26 |
rc-update add nfs default |
| 27 |
/etc/init.d/nfs start |
| 28 |
|
| 29 |
If both client and server side services are running correctly then |
| 30 |
should just work. |
| 31 |
|
| 32 |
Zac |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 35 |
|
| 36 |
iD8DBQFHIQBD/ejvha5XGaMRAjscAKDtMwR9v/kk1si83X6Yw/bL8GscbgCdHGmC |
| 37 |
t2spiSHCT+asZE7afFiJIHc= |
| 38 |
=TrRr |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
-- |
| 41 |
gentoo-user@g.o mailing list |
Archives