On Sun, Dec 09, 2007 at 01:24:23AM +0300, Alexander Gvozdev wrote:
> С какого фига может возникнуть ситуация:
> --------------------
> [root@lina-big ~]# mount -a
> mount.nfs: rpc.statd is not running but is required for remote locking.
>    Either use '-o nolocks' to keep locks local, or start statd.
> mount.nfs: rpc.statd is not running but is required for remote locking.
>    Either use '-o nolocks' to keep locks local, or start statd.
> mount.nfs: rpc.statd is not running but is required for remote locking.
>    Either use '-o nolocks' to keep locks local, or start statd.
> mount.nfs: rpc.statd is not running but is required for remote locking.
>    Either use '-o nolocks' to keep locks local, or start statd.
> mount.nfs: rpc.statd is not running but is required for remote locking.
>    Either use '-o nolocks' to keep locks local, or start statd.
> [root@lina-big ~]#                                               
> -----------------
> apt-cache search statd ничего приличного не даёт.
> С "'-o nolocks" не монтируется.

Параметр называется nolock, statd запускается с помощью service nfslock.
Какая версия пакета, из которого у вас mount.nfs?


-- 
ldv