-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stefan G. Weichinger wrote:
>>>>>> Emerging (1 of 1) x11-libs/libsexy-0.1.11 to /
>>> and then just hangs there, doing nothing.
>> That's right where it attempts to obtain a lock on the required
>> files in ${DISTDIR}. If that's on nfs and nfs isn't behaving
>> properly then it can cause problems like that. Check dmesg.
>
> Correct, my ${DISTDIR} is normally mounted via nfs.
> When I umount it, I can emerge ...
>
> When mounted, dmesg gives me
>
> lockd: cannot monitor ${IP_OF_NFS_SERVER}
> lockd: failed to monitor ${IP_OF_NFS_SERVER}
>
> What can I do to fix this? Restarting the nfs-service on the server did
> not help yet.
There are also nfs services that you need to run on the client side.
Maybe you need to do something like this:
emerge --noreplace nfs-utils
rc-update add nfs default
/etc/init.d/nfs start
If both client and server side services are running correctly then
should just work.
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHIQBD/ejvha5XGaMRAjscAKDtMwR9v/kk1si83X6Yw/bL8GscbgCdHGmC
t2spiSHCT+asZE7afFiJIHc=
=TrRr
-----END PGP SIGNATURE-----
--
[EMAIL PROTECTED] mailing list
