AW: lockd failed to monitor

[Kromer Sven SKKAI <Sven.Kromer@ag.ch>]

Hi

In some Systems the adresses 10.0.0.x give problems (eg. NT) It is bether to
begin with 10.1.1.y.

Kind regards S. Kromer

> -----Ursprüngliche Nachricht-----
> Von:	Ken Yap [SMTP:ken@nlc.net.au]
> Gesendet am:	Dienstag, 12. Oktober 1999 15:12
> An:	netboot@baghira.han.de
> Betreff:	Re: lockd failed to monitor 
> 
> 
> >lockd: failed to monitor 10.0.0.1
> >
> >10.0.0.1 is the IP address of my nfs server.  It happens mostly at boot
> >time (when logging is started) but also occurs whenever locks occur in
> >the nfs-mounted partitions on the clients.  I verified that lockd is
> >configured in the kernel (CONFIG_LOCKD=y).   I am running Redhat 6.0 on
> >a Pentium II.
> >
> >Has anyone experienced this problem on the client?
> 
> Yes, on diskful clients. This seems to be a fault with the knfsd
> implementation and not specific to diskless operation. You could see if
> any of the recent fixes to knfsd help, maybe.
> ==========================================================================
> =
> This Mail was sent to netboot mailing list by:
> Ken Yap <ken@nlc.net.au>
> To get help about this list, send a mail with 'help' as the only string in
> it's body to majordomo@baghira.han.de. If you have problems with this
> list,
> send a mail to netboot-owner@baghira.han.de.
===========================================================================
This Mail was sent to netboot mailing list by:
Kromer Sven  SKKAI <Sven.Kromer@ag.ch>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.