lockd problems

2006-11-03 Thread hendrik
Now I get a lot of these messages On Fri, Nov 03, 2006 at 08:02:09AM -0500, [EMAIL PROTECTED] wrote: ... > Nov 3 07:30:07 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13 > Nov 3 07:30:07 lovesong kernel: lockd: failed to monitor 172.25.1.11 It would appear that my lockd is not configured

lockd problems

2000-10-29 Thread peter karlsson
Hi! Lately, I've gotten Starting NFS common utilities: statd lockdportmap: server localhost not responding, timed out portmap: server localhost not responding, timed out lockd_up: makesock failed, error=-5 portmap: server localhost not responding, timed out lockdsvc: Input/output error . when I

Re: NFS lockd problems

1999-10-12 Thread Brian May
In article <[EMAIL PROTECTED]> you write: >> I have heard that file locking is not implemented in the user >> level server, but you need the kernel level server instead. > >Well, that would explain why it wouldn't work Is this documented >anywhere? I think I saw a message on the linux-kernel

Re: NFS lockd problems

1999-10-10 Thread Greg Wooledge
Brian May ([EMAIL PROTECTED]) wrote: > I have heard that file locking is not implemented in the user > level server, but you need the kernel level server instead. Well, that would explain why it wouldn't work Is this documented anywhere? I did some Usenet searching and came up with an artic

Re: NFS lockd problems

1999-10-10 Thread Brian May
>The problem is that file locking does not work. If I upgrade mutt >to one of the newer versions (e.g., 1.0pre3-1.2), mutt attempts to >lock my mailbox even though I'm using Maildir and not mbox format. >(See bug #44386.) I've also experienced a "hang" when Angband (variants) >attempt to lock the

NFS lockd problems

1999-10-09 Thread Greg Wooledge
NFS server: Linux dwarf 2.2.12 #2 Fri Oct 8 20:52:57 EDT 1999 i686 unknown ii nfs-common 1.4.7-2Common NFS Tools ii nfs-server 2.2beta46-2User space NFS server. NFS client: Linux jekyll 2.2.12 #5 Sat Sep 4 11:28:01 EDT 1999 i586 unknown ii nfs-common 1.4.7-2