o monitor 172.25.1.11
>
> System Events
> =-=-=-=-=-=-=
> Sep 23 10:08:45 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:45 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 10:08:45 lovesong kernel: lockd: cannot monitor 172.25.1.11
> Sep 23 1
On Sat, 27 Nov 2004 11:30:15 +0100, Terje Fåberg wrote:
> (1) initrd creates a new tmpfs
> (2) initrd copies the image of the root file-system
> minus /usr into that tmpfs
> (3) mount /usr from server in read-only mode
> (4) initrd pivots to the tmpfs
>
> This way no data on the server nee
Hello everyone,
Short problem: When mounting an nfs filesystem
I get dozens of error messages, although the mount
seems to work flawlessly:
lockd: cannot monitor 192.168.20.1
Long description: I'm mounting a nfs file system
out of a minimal system in an initrd. In the initrd
i confi
OK, I've got my diskless workstation up running a virgin 2.2r5 and
being served from an AIX 4.3.3 host. All is sweetness and light
except for long repetitions of the subject message. Both hosts are
running lockd and statd but I notice that the Debian box has no files
in '/var/lib/nfs/sm/'.
4 matches
Mail list logo